<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" prefix='bibo: http://purl.org/ontology/bibo/' typeof="bibo:Document">
<head>
<title>JSON-LD Syntax 1.0</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />

<!--
  === NOTA BENE ===
  For the three scripts below, if your spec resides on dev.w3 you can check them
  out in the same tree and use relative links so that they'll work offline,
  -->




<style type="text/css">
  .diff { font-weight:bold; color:#0a3; }
  table, thead, tr, td { padding: 5px; border-width: 1px; border-spacing: 0px; border-style: solid; border-collapse: collapse;}
</style>
<style>/*****************************************************************
 * ReSpec 3 CSS
 * Robin Berjon - http://berjon.com/
 *****************************************************************/

/* --- INLINES --- */
em.rfc2119 { 
    text-transform:     lowercase;
    font-variant:       small-caps;
    font-style:         normal;
    color:              #900;
}

h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
    border: none;
}

dfn {
    font-weight:    bold;
}

a.internalDFN {
    color:  inherit;
    border-bottom:  1px solid #99c;
    text-decoration:    none;
}

a.externalDFN {
    color:  inherit;
    border-bottom:  1px dotted #ccc;
    text-decoration:    none;
}

a.bibref {
    text-decoration:    none;
}

cite .bibref {
    font-style: normal;
}

code {
    color:  #ff4500;
}


/* --- --- */
ol.algorithm { counter-reset:numsection; list-style-type: none; }
ol.algorithm li { margin: 0.5em 0; }
ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }

/* --- TOC --- */
.toc a, .tof a {
    text-decoration:    none;
}

a .secno, a .figno {
    color:  #000;
}

ul.tof, ol.tof {
    list-style: none outside none;
}

.caption {
    margin-top: 0.5em;
    font-style:   italic;
}

/* --- TABLE --- */
table.simple {
    border-spacing: 0;
    border-collapse:    collapse;
    border-bottom:  3px solid #005a9c;
}

.simple th {
    background: #005a9c;
    color:  #fff;
    padding:    3px 5px;
    text-align: left;
}

.simple th[scope="row"] {
    background: inherit;
    color:  inherit;
    border-top: 1px solid #ddd;
}

.simple td {
    padding:    3px 10px;
    border-top: 1px solid #ddd;
}

.simple tr:nth-child(even) {
    background: #f0f6ff;
}

/* --- DL --- */
.section dd > p:first-child {
    margin-top: 0;
}

.section dd > p:last-child {
    margin-bottom: 0;
}

.section dd {
    margin-bottom:  1em;
}

.section dl.attrs dd, .section dl.eldef dd {
    margin-bottom:  0;
}
</style><style>/* --- EXAMPLES --- */
div.example-title {
    min-width: 7.5em;
    color: #b9ab2d;
}
div.example-title span {
    text-transform: uppercase;   
}
aside.example, div.example, div.illegal-example {
    padding: 0.5em;
    margin: 1em 0;
    position: relative;
    clear: both;
}
div.illegal-example { color: red }
div.illegal-example p { color: black }
aside.example, div.example {
    padding: .5em;
    border-left-width: .5em;
    border-left-style: solid;
    border-color: #e0cb52;
    background: #fcfaee;    
}

aside.example div.example {
    border-left-width: .1em;
    border-color: #999;
    background: #fff;
}
aside.example div.example div.example-title {
    color: #999;
}
</style><style>/* --- ISSUES/NOTES --- */
div.issue-title, div.note-title {
    padding-right:  1em;
    min-width: 7.5em;
    color: #b9ab2d;
}
div.issue-title { color: #e05252; }
div.note-title { color: #52e052; }
div.issue-title span, div.note-title span {
    text-transform: uppercase;
}
div.note, div.issue {
    margin-top: 1em;
    margin-bottom: 1em;
}
.note > p:first-child, .issue > p:first-child { margin-top: 0 }
.issue, .note {
    padding: .5em;
    border-left-width: .5em;
    border-left-style: solid;
}
div.issue, div.note {
    padding: 0.5em;
    margin: 1em 0;
    position: relative;
    clear: both;
}
span.note, span.issue { padding: .1em .5em .15em; }

.issue {
    border-color: #e05252;
    background: #fbe9e9;
}
.note {
    border-color: #52e052;
    background: #e9fbe9;
}


</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-ED" />
<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->

<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
<style type='text/css'>
.diff-old-a {
  font-size: smaller;
  color: red;
}

.diff-new { background-color: yellow; }
.diff-chg { background-color: lime; }
.diff-new:before,
.diff-new:after
    { content: "\2191" }
.diff-chg:before, .diff-chg:after
    { content: "\2195" }
.diff-old { text-decoration: line-through; background-color: #FBB; }
.diff-old:before,
.diff-old:after
    { content: "\2193" }
:focus { border: thin red solid}
</style>
</head>


<body>
<div class="head">
<p>
<a href="http://www.w3.org/">
<img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" />
</a>
</p>
<h1 class="title" id="title">
JSON-LD
Syntax
1.0
</h1>
<h2 id="subtitle">
A
<del class="diff-old">Context-based
</del>
JSON
Serialization
for
Linking
Data
</h2>
<h2 id="w3c-editor-s-draft-25-december-2012">
<abbr title="World Wide Web Consortium">
W3C
</abbr>
Editor's
Draft
<del class="diff-old">30
September
</del>
<ins class="diff-chg">25
December
</ins>
2012
</h2>
<dl>
<dt>
This
version:
</dt>
<dd>
<a href="http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html">
http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html
</a>
</dd>
<dt>
Latest
published
version:
</dt>
<dd>
<a href="http://www.w3.org/TR/json-ld-syntax/">
http://www.w3.org/TR/json-ld-syntax/
</a>
</dd>
<dt>
Latest
editor's
draft:
</dt>
<dd>
<a href="http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html">
http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html
</a>
</dd>
<dt>
Editors:
</dt>
<dd rel="bibo:editor" inlist="">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">
Manu
Sporny
</a>,
<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
Digital
Bazaar
</a>
</span>
</dd>
<dd rel="bibo:editor" inlist="">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">
Gregg
Kellogg
</a>,
<a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">
Kellogg
Associates
</a>
</span>
</dd>
<dd rel="bibo:editor" inlist="">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">
Markus
Lanthaler
</a>,
<a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">
Graz
University
of
Technology
</a>
</span>
</dd>
<dt>
Authors:
</dt>
<dd rel="dcterms:contributor">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://digitalbazaar.com/">
Manu
Sporny
</a>,
<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
Digital
Bazaar
</a>
</span>
</dd>
<dd rel="dcterms:contributor">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">
Dave
Longley
</a>,
<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
Digital
Bazaar
</a>
</span>
</dd>
<dd rel="dcterms:contributor">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">
Gregg
Kellogg
</a>,
<a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">
Kellogg
Associates
</a>
</span>
</dd>
<dd rel="dcterms:contributor">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">
Markus
Lanthaler
</a>,
<a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">
Graz
University
of
Technology
</a>
</span>
</dd>
<dd rel="dcterms:contributor">
<span typeof="foaf:Person">
<a rel="foaf:homepage" property="foaf:name" content="Mark Birbeck" href="http://webbackplane.com/">
Mark
Birbeck
</a>,
<a rel="foaf:workplaceHomepage" href="http://webbackplane.com/">
Backplane
Ltd.
</a>
</span>
</dd>
</dl>
<p>
This
document
is
also
available
in
this
non-normative
format:
<a href="diff-20120930.html">
diff
to
previous
version
</a>
</p>
<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
Copyright
</a>
©
2010-2012
<a href="http://www.w3.org/">
<abbr title="World Wide Web Consortium">
W3C
</abbr>
</a>
<sup>
®
</sup>
(
<a href="http://www.csail.mit.edu/">
<abbr title="Massachusetts Institute of Technology">
MIT
</abbr>
</a>,
<a href="http://www.ercim.eu/">
<abbr title="European Research Consortium for Informatics and Mathematics">
ERCIM
</abbr>
</a>,
<a href="http://www.keio.ac.jp/">
Keio
</a>
),
All
Rights
Reserved.
<abbr title="World Wide Web Consortium">
W3C
</abbr>
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">
liability
</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">
trademark
</a>
and
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">
document
use
</a>
rules
apply.
</p>
<hr />
</div>
<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter">
<h2>
Abstract
</h2>
<p>
JSON
has
proven
to
be
a
highly
useful
object
serialization
and
messaging
format.
In
an
attempt
to
harmonize
the
representation
of
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
Linked
Data
</a>
in
JSON,
this
specification
outlines
a
common
JSON
representation
format
for
expressing
directed
graphs;
mixing
both
Linked
Data
and
non-Linked
Data
in
a
single
document.
</p>
</section>
<section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter">
<h2>
Status
of
This
Document
</h2>
<p>
<em>
This
section
describes
the
status
of
this
document
at
the
time
of
its
publication.
Other
documents
may
supersede
this
document.
A
list
of
current
<abbr title="World Wide Web Consortium">
W3C
</abbr>
publications
and
the
latest
revision
of
this
technical
report
can
be
found
in
the
<a href="http://www.w3.org/TR/">
<abbr title="World Wide Web Consortium">
W3C
</abbr>
technical
reports
index
</a>
at
http://www.w3.org/TR/.
</em>
</p>
<p>
This
document
has
been
under
development
for
over
20
months
in
the
JSON
for
Linking
Data
Community
Group.
The
document
has
recently
been
transferred
to
the
RDF
Working
Group
for
review,
improvement,
and
publication
along
the
Recommendation
track.
The
specification
has
undergone
significant
development,
review,
and
changes
during
the
course
of
the
last
20
months.
</p>
<p>
There
are
<del class="diff-old">currently
</del>
<ins class="diff-chg">several
independent
</ins>
<a href="http://json-ld.org/#impl">
<del class="diff-old">five
</del>
interoperable
implementations
</a>
of
this
specification.
There
is
a
<a href="https://github.com/json-ld/json-ld.org/tree/main/test-suite">
fairly
complete
test
suite
</a>
and
a
<a href="http://json-ld.org/playground/">
live
JSON-LD
editor
</a>
that
is
capable
of
demonstrating
the
features
described
in
this
document.
While
development
on
implementations,
the
test
suite
and
the
live
editor
will
continue,
they
are
believed
to
be
mature
enough
to
be
integrated
into
a
non-production
system
at
this
point
in
time
with
the
expectation
that
they
could
be
used
in
a
production
system
within
the
next
year.
</p>
<p>
There
are
a
number
of
ways
that
one
may
participate
in
the
development
of
this
specification:
</p>
<ul>
<li>
If
you
want
to
make
sure
that
your
feedback
is
formally
addressed
by
the
RDF
Working
Group,
you
should
send
it
to
public-rdf-comments:
<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">
public-rdf-comments@w3.org
</a>
</li>
<li>
Ad-hoc
technical
discussion
primarily
occurs
on
the
public
community
mailing
list:
<a href="http://lists.w3.org/Archives/Public/public-linked-json/">
public-linked-json@w3.org
</a>
</li>
<li>
<a href="http://json-ld.org/minutes/">
Public
JSON-LD
Community
Group
teleconferences
</a>
are
held
on
Tuesdays
at
1500UTC
every
week.
</li>
<li>
RDF
Working
Group
teleconferences
are
held
on
Wednesdays
at
1500UTC
every
week.
Participation
is
limited
to
RDF
Working
Group
members.
</li>
<li>
Specification
bugs
and
issues
should
be
reported
in
the
<a href="https://github.com/json-ld/json-ld.org/issues">
issue
tracker
</a>
if
you
do
not
want
to
send
an
e-mail
to
the
public-rdf-comments
mailing
list.
</li>
<li>
<a href="https://github.com/json-ld/json-ld.org/tree/main/spec">
Source
code
</a>
for
the
specification
can
be
found
on
Github.
</li>
<li>
The
<a href="http://webchat.freenode.net/?channels=json-ld">
#json-ld
</a>
IRC
channel
is
available
for
real-time
discussion
on
irc.freenode.net.
</li>
</ul>
<p>
This
document
was
published
by
the
<a href="http://www.w3.org/2011/rdf-wg/">
RDF
Working
Group
</a>
as
an
Editor's
Draft.
If
you
wish
to
make
comments
regarding
this
document,
please
send
them
to
<a href="mailto:public-rdf-comments@w3.org">
public-rdf-comments@w3.org
</a>
(
<a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe">
subscribe
</a>,
<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">
archives
</a>
).
All
feedback
is
welcome.
</p>
<p>
Publication
as
an
Editor's
Draft
does
not
imply
endorsement
by
the
<abbr title="World Wide Web Consortium">
W3C
</abbr>
Membership.
This
is
a
draft
document
and
may
be
updated,
replaced
or
obsoleted
by
other
documents
at
any
time.
It
is
inappropriate
to
cite
this
document
as
other
than
work
in
progress.
</p>
<p>
This
document
was
produced
by
a
group
operating
under
the
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">
5
February
2004
<abbr title="World Wide Web Consortium">
W3C
</abbr>
Patent
Policy
</a>.
<abbr title="World Wide Web Consortium">
W3C
</abbr>
maintains
a
<a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure">
public
list
of
any
patent
disclosures
</a>
made
in
connection
with
the
deliverables
of
the
group;
that
page
also
includes
instructions
for
disclosing
a
patent.
An
individual
who
has
actual
knowledge
of
a
patent
which
the
individual
believes
contains
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
Essential
Claim(s)
</a>
must
disclose
the
information
in
accordance
with
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
section
6
of
the
<abbr title="World Wide Web Consortium">
W3C
</abbr>
Patent
Policy
</a>.
</p>
</section>
<section id="toc">
<h2 class="introductory">
Table
of
Contents
</h2>
<ul class="toc">
<li class="tocline">
<a href="#introduction" class="tocxref">
<span class="secno">
1.
</span>
Introduction
</a>
<ul class="toc">
<li class="tocline">
<a href="#how-to-read-this-document" class="tocxref">
<span class="secno">
1.1
</span>
How
to
Read
this
Document
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#design-goals-and-rationale" class="tocxref">
<span class="secno">
2.
</span>
Design
Goals
and
Rationale
</a>
</li>
<li class="tocline">
<a href="#terminology" class="tocxref">
<span class="secno">
3.
</span>
<del class="diff-old">Basic
Concepts
</del>
<ins class="diff-chg">Terminology
</ins>
</a>
<ul class="toc">
<li class="tocline">
<a href="#general-terminology" class="tocxref">
<span class="secno">
3.1
</span>
<del class="diff-old">Benefits
of
JSON-LD
</del>
<ins class="diff-chg">General
Terminology
</ins>
</a>
</li>
<li class="tocline">
<a href="#syntax-tokens-and-keywords" class="tocxref">
<span class="secno">
3.2
</span>
<del class="diff-old">JSON-LD
Data
Model
</del>
<ins class="diff-chg">Syntax
Tokens
and
Keywords
</ins>
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#conformance" class="tocxref">
<span class="secno">
<del class="diff-old">3.3
</del>
<ins class="diff-chg">4.
</ins>
</span>
<del class="diff-old">General
Terminology
</del>
<ins class="diff-chg">Conformance
</ins>
</a>
</li>
<li class="tocline">
<a href="#basic-concepts" class="tocxref">
<span class="secno">
<del class="diff-old">3.4
</del>
<ins class="diff-chg">5.
</ins>
</span>
<del class="diff-old">Syntax
Tokens
and
Keywords
</del>
<ins class="diff-chg">Basic
Concepts
</ins>
</a>
<ul class="toc">
<li class="tocline">
<a href="#the-context" class="tocxref">
<span class="secno">
<del class="diff-old">3.5
</del>
<ins class="diff-chg">5.1
</ins>
</span>
The
Context
</a>
</li>
<li class="tocline">
<a href="#from-json-to-json-ld" class="tocxref">
<span class="secno">
<del class="diff-old">3.6
</del>
<ins class="diff-chg">5.2
</ins>
</span>
From
JSON
to
JSON-LD
</a>
</li>
<li class="tocline">
<a href="#iris" class="tocxref">
<span class="secno">
<del class="diff-old">3.7
</del>
<ins class="diff-chg">5.3
</ins>
</span>
IRIs
</a>
</li>
<li class="tocline">
<a href="#node-identifiers" class="tocxref">
<span class="secno">
<del class="diff-old">3.8
</del>
<ins class="diff-chg">5.4
</ins>
</span>
Node
Identifiers
</a>
</li>
<li class="tocline">
<a href="#specifying-the-type" class="tocxref">
<span class="secno">
<del class="diff-old">3.9
</del>
<ins class="diff-chg">5.5
</ins>
</span>
Specifying
the
Type
</a>
</li>
<li class="tocline">
<a href="#string-internationalization" class="tocxref">
<span class="secno">
<del class="diff-old">3.10
</del>
<ins class="diff-chg">5.6
</ins>
</span>
String
Internationalization
</a>
</li>
<li class="tocline">
<a href="#json-ld-syntax" class="tocxref">
<span class="secno">
<del class="diff-old">3.11
</del>
<ins class="diff-chg">5.7
</ins>
</span>
JSON-LD
Syntax
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#advanced-concepts" class="tocxref">
<span class="secno">
<del class="diff-old">4.
</del>
<ins class="diff-chg">6.
</ins>
</span>
Advanced
Concepts
</a>
<ul class="toc">
<li class="tocline">
<a href="#compact-iris" class="tocxref">
<span class="secno">
<del class="diff-old">4.1
</del>
<ins class="diff-chg">6.1
</ins>
</span>
Compact
IRIs
</a>
</li>
<li class="tocline">
<a href="#typed-values" class="tocxref">
<span class="secno">
<del class="diff-old">4.2
</del>
<ins class="diff-chg">6.2
</ins>
</span>
Typed
Values
</a>
</li>
<li class="tocline">
<a href="#language-tagged-strings" class="tocxref">
<span class="secno">
<del class="diff-old">4.3
</del>
<ins class="diff-chg">6.3
</ins>
</span>
Language-tagged
Strings
</a>
</li>
<li class="tocline">
<a href="#referencing-contexts-from-json-documents" class="tocxref">
<span class="secno">
<del class="diff-old">4.4
</del>
<ins class="diff-chg">6.4
</ins>
</span>
Referencing
Contexts
from
JSON
Documents
</a>
</li>
<li class="tocline">
<a href="#expanded-term-definition" class="tocxref">
<span class="secno">
<del class="diff-old">4.5
</del>
<ins class="diff-chg">6.5
</ins>
</span>
Expanded
Term
Definition
</a>
</li>
<li class="tocline">
<a href="#type-coercion" class="tocxref">
<span class="secno">
<del class="diff-old">4.6
</del>
<ins class="diff-chg">6.6
</ins>
</span>
Type
Coercion
</a>
</li>
<li class="tocline">
<a href="#property-generators" class="tocxref">
<span class="secno">
<del class="diff-old">4.7
</del>
<ins class="diff-chg">6.7
</ins>
</span>
Property
Generators
</a>
</li>
<li class="tocline">
<a href="#iri-expansion-within-a-context" class="tocxref">
<span class="secno">
<del class="diff-old">4.8
</del>
<ins class="diff-chg">6.8
</ins>
</span>
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
Expansion
Within
a
Context
</a>
</li>
<li class="tocline">
<a href="#sets-and-lists" class="tocxref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
Sets
and
Lists
</a>
</li>
<li class="tocline">
<a href="#embedding" class="tocxref">
<span class="secno">
<del class="diff-old">4.10
</del>
<ins class="diff-chg">6.10
</ins>
</span>
Embedding
</a>
</li>
<li class="tocline">
<a href="#named-graphs" class="tocxref">
<span class="secno">
<del class="diff-old">4.11
</del>
<ins class="diff-chg">6.11
</ins>
</span>
Named
Graphs
</a>
</li>
<li class="tocline">
<a href="#identifying-blank-nodes" class="tocxref">
<span class="secno">
<del class="diff-old">4.12
</del>
<ins class="diff-chg">6.12
</ins>
</span>
Identifying
<del class="diff-old">Unlabeled
</del>
<ins class="diff-chg">Blank
</ins>
Nodes
</a>
</li>
<li class="tocline">
<a href="#aliasing-keywords" class="tocxref">
<span class="secno">
<del class="diff-old">4.13
</del>
<ins class="diff-chg">6.13
</ins>
</span>
Aliasing
Keywords
</a>
</li>
<li class="tocline">
<a href="#data-annotations" class="tocxref">
<span class="secno">
<ins class="diff-new">6.14
</ins></span><ins class="diff-new">
Data
Annotations
</ins></a></li><li class="tocline"><a href="#explicitly-ignoring-data" class="tocxref"><span class="secno"><ins class="diff-new">
6.15
</ins></span><ins class="diff-new">
Explicitly
Ignoring
Data
</ins></a></li><li class="tocline">
<a href="#expanded-document-form" class="tocxref">
<span class="secno">
<del class="diff-old">4.14
</del>
<ins class="diff-chg">6.16
</ins>
</span>
Expanded
Document
Form
</a>
</li>
<li class="tocline">
<a href="#compact-document-form" class="tocxref">
<span class="secno">
<del class="diff-old">4.15
</del>
<ins class="diff-chg">6.17
</ins>
</span>
Compact
Document
Form
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#data-model" class="tocxref">
<span class="secno">
A.
</span>
<ins class="diff-new">Data
Model
</ins></a></li><li class="tocline"><a href="#json-ld-grammar" class="tocxref"><span class="secno"><ins class="diff-new">
B.
</ins></span>
JSON-LD
Grammar
</a>
<ul class="toc">
<li class="tocline">
<a href="#grammar-node-object" class="tocxref">
<span class="secno">
<del class="diff-old">A.1
</del>
<ins class="diff-chg">B.1
</ins>
</span>
Node
<del class="diff-old">Definition
</del>
<ins class="diff-chg">Object
</ins>
</a>
</li>
<li class="tocline">
<a href="#grammar-term-reference" class="tocxref">
<span class="secno">
<del class="diff-old">A.2
</del>
<ins class="diff-chg">B.2
</ins>
</span>
<del class="diff-old">Node
Reference
</del>
<ins class="diff-chg">Term
</ins>
</a>
</li>
<li class="tocline">
<a href="#grammar-language-map" class="tocxref">
<span class="secno">
<del class="diff-old">A.3
</del>
<ins class="diff-chg">B.3
</ins>
</span>
Language
Map
</a>
</li>
<li class="tocline">
<a href="#grammar-annotation-map" class="tocxref">
<span class="secno">
<ins class="diff-new">B.4
</ins></span><ins class="diff-new">
Annotation
Map
</ins></a></li><li class="tocline">
<a href="#grammar-expanded-values" class="tocxref">
<span class="secno">
<del class="diff-old">A.4
</del>
<ins class="diff-chg">B.5
</ins>
</span>
Expanded
Values
</a>
</li>
<li class="tocline">
<a href="#grammar-set-list" class="tocxref">
<span class="secno">
<del class="diff-old">A.5
</del>
<ins class="diff-chg">B.6
</ins>
</span>
List
and
Set
Values
</a>
</li>
<li class="tocline">
<a href="#grammar-context" class="tocxref">
<span class="secno">
<del class="diff-old">A.6
</del>
<ins class="diff-chg">B.7
</ins>
</span>
Context
Definition
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#relationship-to-rdf" class="tocxref">
<span class="secno">
<del class="diff-old">B.
</del>
<ins class="diff-chg">C.
</ins>
</span>
Relationship
to
<del class="diff-old">Other
Linked
Data
Formats
and
Data
Models
</del>
<ins class="diff-chg">RDF
</ins>
</a>
</li>
<li class="tocline">
<a href="#relationship-to-other-linked-data-formats" class="tocxref">
<span class="secno">
<del class="diff-old">B.1
</del>
<ins class="diff-chg">D.
</ins>
</span>
<del class="diff-old">RDF
</del>
<ins class="diff-chg">Relationship
to
Other
Linked
Data
Formats
</ins>
</a>
<ul class="toc">
<li class="tocline">
<a href="#turtle" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.1
</del>
<ins class="diff-chg">D.1
</ins>
</span>
Turtle
</a>
<ul class="toc">
<li class="tocline">
<a href="#prefix-definitions" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.1.1
</del>
<ins class="diff-chg">D.1.1
</ins>
</span>
Prefix
definitions
</a>
</li>
<li class="tocline">
<a href="#embedding-1" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.1.2
</del>
<ins class="diff-chg">D.1.2
</ins>
</span>
Embedding
</a>
</li>
<li class="tocline">
<a href="#lists" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.1.3
</del>
<ins class="diff-chg">D.1.3
</ins>
</span>
Lists
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#rdfa" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.2
</del>
<ins class="diff-chg">D.2
</ins>
</span>
RDFa
</a>
</li>
<li class="tocline">
<a href="#microformats" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.3
</del>
<ins class="diff-chg">D.3
</ins>
</span>
Microformats
</a>
</li>
<li class="tocline">
<a href="#microdata" class="tocxref">
<span class="secno">
<del class="diff-old">B.1.4
</del>
<ins class="diff-chg">D.4
</ins>
</span>
Microdata
</a>
</li>
</ul>
</li>
<li class="tocline">
<a href="#iana-considerations" class="tocxref">
<span class="secno">
<del class="diff-old">B.2
</del>
<ins class="diff-chg">E.
</ins>
</span>
IANA
Considerations
</a>
</li>
<li class="tocline">
<a href="#acknowledgements" class="tocxref">
<span class="secno">
<del class="diff-old">B.3
</del>
<ins class="diff-chg">F.
</ins>
</span>
Acknowledgements
</a>
</li>
<li class="tocline">
<a href="#references" class="tocxref">
<span class="secno">
<del class="diff-old">C.
</del>
<ins class="diff-chg">G.
</ins>
</span>
References
</a>
<ul class="toc">
<li class="tocline">
<a href="#normative-references" class="tocxref">
<span class="secno">
<del class="diff-old">C.1
</del>
<ins class="diff-chg">G.1
</ins>
</span>
Normative
references
</a>
</li>
<li class="tocline">
<a href="#informative-references" class="tocxref">
<span class="secno">
<del class="diff-old">C.2
</del>
<ins class="diff-chg">G.2
</ins>
</span>
Informative
references
</a>
</li>
</ul>
</li>
</ul>
</section>
<section class="informative" id="introduction">
<h2>
<span class="secno">
1.
</span>
Introduction
</h2>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
<del class="diff-old">JSON,
as
specified
in
[
</del>
<del class="diff-old">RFC4627
],
is
a
simple
language
for
representing
data
on
the
Web.
</del>
<dfn title="linked_data" id="dfn-linked_data">
Linked
Data
</dfn>
is
a
technique
for
creating
a
network
of
inter-connected
data
across
different
<del class="diff-old">Web
</del>
documents
and
Web
sites.
<del class="diff-old">A
document
in
this
data
network
is
typically
identified
using
an
</del>
<ins class="diff-chg">In
general,
Linked
Data
has
four
properties:
1)
it
uses
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">(Internationalized
Resource
Identifier).
A
software
program
can
typically
follow
an
IRI
just
like
you
follow
a
URL
by
putting
</del>
<ins class="diff-chg">to
name
things;
2)
</ins>
it
<del class="diff-old">into
your
browser's
location
bar.
By
following
IRIs,
a
software
program
can
find
</del>
<ins class="diff-chg">uses
HTTP
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a><ins class="diff-chg">
for
those
names;
3)
the
name
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a>,<ins class="diff-chg">
when
dereferenced,
provide
</ins>
more
information
about
the
<del class="diff-old">document
</del>
<ins class="diff-chg">name;
</ins>
and
<ins class="diff-new">4)
</ins>
the
<del class="diff-old">thing
s
that
the
document
describes.
</del>
<ins class="diff-chg">data
expresses
links
to
data
on
other
Web
sites.
</ins>
These
<del class="diff-old">things
may
also
be
identified
using
IRI
s.
The
IRI
allows
a
software
program
</del>
<ins class="diff-chg">properties
allow
data
published
on
the
Web
</ins>
to
<ins class="diff-new">work
much
like
Web
pages
do
today.
One
can
</ins>
start
at
one
<del class="diff-old">document
</del>
<ins class="diff-chg">piece
of
Linked
Data,
</ins>
and
follow
<ins class="diff-new">the
</ins>
links
to
other
<del class="diff-old">documents
or
things
in
order
to
learn
more
about
all
</del>
<ins class="diff-chg">pieces
</ins>
of
<del class="diff-old">the
documents
and
things
described
</del>
<ins class="diff-chg">data
that
are
hosted
</ins>
on
<ins class="diff-new">different
sites
across
</ins>
the
Web.
</p>
<p>
JSON-LD
is
designed
as
a
lightweight
syntax
<del class="diff-old">that
can
be
used
</del>
to
express
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
Linked
Data
<del class="diff-old">.
</del>
</a>
<ins class="diff-chg">in
JSON
[
</ins><cite><a class="bibref" href="#bib-RFC4627"><ins class="diff-chg">
RFC4627
</ins></a></cite><ins class="diff-chg">
].
</ins>
It
is
primarily
intended
to
be
a
way
to
use
Linked
Data
in
<del class="diff-old">Javascript
and
other
</del>
Web-based
programming
environments.
It
is
also
useful
when
building
<del class="diff-old">inter-operable
</del>
<ins class="diff-chg">interoperable
</ins>
Web
services
and
when
storing
Linked
Data
in
JSON-based
<del class="diff-old">document
</del>
storage
engines.
<del class="diff-old">It
</del>
<ins class="diff-chg">Since
JSON-LD
</ins>
is
<del class="diff-old">practical
and
designed
to
be
as
simple
as
possible,
utilizing
</del>
<ins class="diff-chg">100%
compatible
with
JSON
</ins>
the
large
number
of
JSON
parsers
and
libraries
available
<del class="diff-old">today.
</del>
<ins class="diff-chg">today
can
be
reused.
Additionally
to
all
the
features
JSON
provides,
JSON-LD
introduces:
</ins>
</p>
<del class="diff-old">The
syntax
does
not
necessarily
require
applications
</del>
<ul>
<li>
<ins class="diff-chg">a
universal
identifier
mechanism
for
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-chg">
JSON
objects
</ins></a><ins class="diff-chg">
via
the
use
of
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a>,</li><li><ins class="diff-chg">
a
way
</ins>
to
<del class="diff-old">change
their
JSON,
but
allows
</del>
<ins class="diff-chg">disambiguate
the
keys
used
between
multiple
JSON
documents
by
mapping
them
to
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a><ins class="diff-chg">
via
a
</ins><a class="tref internalDFN" title="context" href="#dfn-context"><ins class="diff-chg">
context
</ins></a>,</li><li><ins class="diff-chg">
a
mechanism
in
which
a
value
in
a
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-chg">
JSON
object
</ins></a><ins class="diff-chg">
may
refer
to
a
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-chg">
JSON
object
</ins></a><ins class="diff-chg">
on
a
different
site
on
the
Web,
</ins></li><li><ins class="diff-chg">
the
ability
to
express
the
language
associated
with
a
</ins><a class="tref internalDFN" title="string" href="#dfn-string"><ins class="diff-chg">
string
</ins></a></li><li><ins class="diff-chg">
a
way
to
associate
datatypes
with
values
such
as
dates,
times,
weights,
and
distances,
</ins></li><li><ins class="diff-chg">
and
a
facility
to
express
</ins>
one
<ins class="diff-new">or
more
directed
graphs,
such
as
a
social
network,
in
a
single
document.
</ins></li></ul><p><ins class="diff-new">
Developers
that
require
any
of
the
facilities
listed
above
or
need
</ins>
to
<del class="diff-old">easily
add
meaning
by
simply
adding
</del>
<ins class="diff-chg">serialize
an
RDF
graph
</ins>
or
<del class="diff-old">referencing
</del>
<ins class="diff-chg">dataset
[
</ins><cite><a class="bibref" href="#bib-RDF-CONCEPTS"><ins class="diff-chg">
RDF-CONCEPTS
</ins></a></cite><ins class="diff-chg">
]
in
</ins>
a
<del class="diff-old">context.
</del>
<ins class="diff-chg">JSON-based
syntax
will
find
JSON-LD
of
interest.
</ins>
The
syntax
is
designed
to
not
disturb
already
deployed
systems
running
on
JSON,
but
provide
a
smooth
upgrade
path
from
JSON
to
JSON-LD.
<del class="diff-old">Finally,
the
format
is
intended
to
be
easy
to
parse,
efficient
to
generate,
and
can
operate
inside
of
devices
that
contain
very
little
memory.
</del>
</p>
<section id="how-to-read-this-document">
<h3>
<span class="secno">
1.1
</span>
How
to
Read
this
Document
</h3>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
This
document
is
a
detailed
specification
for
a
serialization
of
Linked
Data
in
JSON.
The
document
is
primarily
intended
for
the
following
audiences:
</p>
<ul>
<li>
Software
developers
that
want
to
encode
Linked
Data
in
a
variety
of
programing
languages
that
can
use
JSON.
</li>
<li>
Software
developers
that
want
to
understand
the
design
decisions
and
language
syntax
for
JSON-LD.
</li>
<li>
Software
developers
that
want
to
implement
processors
and
APIs
for
JSON-LD.
</li>
</ul>
<p>
This
specification
does
not
describe
the
programming
interfaces
for
the
JSON-LD
Syntax.
The
specification
that
describes
the
programming
interfaces
for
JSON-LD
documents
is
the
JSON-LD
Application
Programming
Interface
[
<cite>
<a class="bibref" href="#bib-JSON-LD-API">
JSON-LD-API
</a>
</cite>
].
</p>
<p>
To
understand
the
basics
in
this
specification
you
must
first
be
familiar
with
JSON,
which
is
detailed
in
[
<cite>
<a class="bibref" href="#bib-RFC4627">
RFC4627
</a>
</cite>
].
</p>
</section>
</section>
<section class="informative" id="design-goals-and-rationale">
<h2>
<span class="secno">
2.
</span>
Design
Goals
and
Rationale
</h2>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
A
number
of
design
goals
were
established
before
the
creation
of
this
markup
language:
</p>
<dl>
<dt>
Simplicity
</dt>
<dd>
No
extra
processors
or
software
libraries
should
be
necessary
to
use
JSON-LD
in
its
most
basic
form.
The
language
will
provide
developers
with
a
very
easy
learning
curve.
Developers
<del class="diff-old">need
</del>
only
<ins class="diff-new">need
to
</ins>
know
JSON
and
two
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keywords
</a>
(
<code>
@context
</code>
and
<code>
@id
</code>
)
to
use
the
basic
functionality
in
JSON-LD.
</dd>
<dt>
Compatibility
</dt>
<dd>
The
JSON-LD
markup
must
be
100%
compatible
with
JSON.
This
ensures
that
all
of
the
standard
JSON
libraries
work
seamlessly
with
JSON-LD
documents.
</dd>
<dt>
Expressiveness
</dt>
<dd>
The
syntax
must
be
able
to
express
directed
graphs,
which
have
been
proven
to
be
able
to
express
almost
every
real
world
data
model.
</dd>
<dt>
Terseness
</dt>
<dd>
The
JSON-LD
syntax
must
be
very
terse
and
human
readable,
requiring
as
little
effort
as
possible
from
the
developer.
</dd>
<dt>
Zero
Edits,
most
of
the
time
</dt>
<dd>
JSON-LD
must
provide
a
<a href="#referencing-contexts-from-json-documents">
mechanism
</a>
that
allows
developers
to
<del class="diff-old">specify
</del>
<ins class="diff-chg">reference
</ins>
<a class="tref internalDFN" title="context" href="#dfn-context">
<del class="diff-old">context
</del>
<ins class="diff-chg">contexts
</ins>
</a>
in
<del class="diff-old">a
way
that
is
out-of-band.
</del>
<ins class="diff-chg">responses
using
plain
old
JSON.
</ins>
This
allows
organizations
that
have
already
deployed
large
JSON-based
infrastructure
to
<del class="diff-old">add
meaning
to
their
JSON
documents
</del>
<ins class="diff-chg">use
JSON-LD's
features
</ins>
in
a
way
that
is
not
disruptive
to
their
day-to-day
operations
and
is
transparent
to
their
current
customers.
At
times,
mapping
JSON
to
a
graph
representation
can
become
difficult.
In
these
instances,
rather
than
having
JSON-LD
support
an
esoteric
use
case,
we
chose
not
to
support
the
use
case
and
support
a
simplified
syntax
instead.
So,
while
Zero
Edits
is
a
design
goal,
it
is
not
always
possible
without
adding
great
complexity
to
the
language.
</dd>
<dt>
One-pass
Processing
</dt>
<dd>
JSON-LD
supports
one-pass
processing,
which
results
in
a
very
small
memory
footprint
when
processing
documents.
For
example,
to
expand
a
JSON-LD
document
from
a
compacted
form,
only
one
pass
is
required
over
the
data.
</dd>
<del class="diff-old">Linked
Data-centric
The
focus
on
Linked
Data
is
placed
at
a
much
higher
priority
than
the
focus
on
the
Semantic
Web.
One
outcome
of
this
ordering
of
priorities
is
an
aggressively
reduced
focus
on
the
Semantic
Web
stack
(RDF
[
RDF-CONCEPTS
],
TURTLE
[
TURTLE-TR
],
triple
stores,
and
SPARQL
[
RDF-SPARQL-QUERY
]).
While
this
may
be
off-putting
to
proponents
of
the
Semantic
Web,
the
audience
for
this
specification
are
Web
developers
that
want
a
gentler
introduction
and
a
simpler
technology
stack
for
using
Linked
Data
in
their
Web
applications.
Semantic
Web
concepts,
such
as
conversion
to
and
from
RDF,
are
fully
supported
by
JSON-LD,
but
the
implementation
of
these
features
are
not
elaborated
upon
in
this
specification.
See
B.
Relationship
to
Other
Linked
Data
Formats
and
Data
Models
for
more
information
about
how
JSON-LD
integrates
into
the
more
traditional
Semantic
Web
stack.
</del>
</dl>
</section>
<section class="normative" id="terminology">
<h2>
<span class="secno">
3.
</span>
<del class="diff-old">Basic
Concepts
</del>
<ins class="diff-chg">Terminology
</ins>
</h2>
<del class="diff-old">This
section
is
normative.
JSON-LD
is
designed
to
ensure
that
Linked
Data
concepts
can
be
marked
up
in
a
way
that
is
simple
to
understand
and
create
by
Web
authors.
In
many
cases,
regular
JSON
markup
can
become
Linked
Data
with
the
simple
addition
of
a
context
.
As
more
JSON-LD
features
are
used,
more
semantics
are
added
to
the
JSON
markup.
</del>
<section id="general-terminology">
<h3>
<span class="secno">
3.1
</span>
<del class="diff-old">Benefits
of
JSON-LD
</del>
<ins class="diff-chg">General
Terminology
</ins>
</h3>
<p>
<del class="diff-old">JSON
provides
a
number
of
benefits
to
software
developers
that
need
to
serialize
data:
It
is
easy
for
humans
to
read
and
write.
It
is
easy
for
machines
to
parse
and
generate.
It
has
a
syntax
that
is
familiar
across
a
large
number
of
programming
languages.
It
is
capable
of
representing
many
different
types
of
data
using
two
universal
data
structures;
a
collection
of
key-value
pairs
and
lists.
JSON
has
become
a
very
popular
data-interchange
format
on
the
Web,
particularly
for
REST
-based
Web
Services.
Unfortunately,
it
has
a
number
of
short-comings
that
other
Web-native
data
formats
do
not
have:
There
is
no
standardized,
universal
identifier
mechanism
for
JSON
object
s.
The
meaning
of
the
keys
used
in
a
JSON
object
s
are
ambiguous
and
often
conflict
with
other
data
published
on
the
Web.
There
is
no
standardized
way
for
a
value
in
a
JSON
object
to
refer
to
a
JSON
object
on
a
different
site
on
the
Web.
A
developer
cannot
express
</del>
<ins class="diff-chg">This
document
uses
</ins>
the
<del class="diff-old">language
associated
with
a
string
value
in
a
standardized
manner.
There
is
no
standard
mechanism
to
associate
datatypes
with
values
such
as
dates,
times,
weights,
and
distances.
There
is
no
facility
to
express
a
Web
of
information
(directed
graph),
such
</del>
<ins class="diff-chg">following
terms
</ins>
as
<del class="diff-old">a
social
network,
</del>
<ins class="diff-chg">defined
</ins>
in
<del class="diff-old">a
standardized
manner.
JSON-LD
is
a
web-native
standard,
is
100%
compatible
with
JSON,
provides
all
of
the
facilities
that
JSON
provides,
and
extends
the
language
to
provide
the
following
core
advantages:
A
universal
identifier
mechanism
for
</del>
JSON
<del class="diff-old">object
s
via
the
use
of
IRI
</del>
<ins class="diff-chg">[
</ins><cite>
<a class="bibref" href="#bib-RFC4627">
<ins class="diff-new">RFC4627
</ins>
</a>
<del class="diff-old">s.
A
way
to
dis-ambiguate
the
keys
used
between
multiple
JSON
documents
by
mapping
them
to
IRI
</del>
<del class="diff-old">s
via
a
context
.
A
mechanism
in
which
a
value
in
a
JSON
object
may
refer
to
a
JSON
object
on
a
different
site
on
the
Web.
The
ability
to
express
the
language
associated
with
a
string
value.
A
way
to
associate
datatypes
with
values
such
as
dates,
times,
weights,
and
distances.
A
facility
</del>
</cite>
<ins class="diff-chg">].
Refer
</ins>
to
<del class="diff-old">express
one
or
more
directed
graphs,
such
as
a
social
network,
in
a
single
document.
Developers
that
require
any
of
</del>
the
<del class="diff-old">facilities
listed
above
will
find
JSON-LD
of
interest.
3.2
JSON-LD
Data
Model
Linked
Data
is
a
way
of
publishing
data
on
the
Web.
In
general,
Linked
Data
has
four
properties;
1)
It
uses
IRI
s
to
name
</del>
<em>
<del class="diff-old">things
,
2)
It
uses
HTTP
IRI
s
for
those
names,
3)
The
name
links,
when
followed,
provide
more
information
about
the
name,
and
4)
The
data
expresses
links
to
data
on
other
Web
sites.
These
properties
allow
data
published
on
the
Web
to
work
much
like
Web
pages
do
today.
One
can
start
at
one
piece
of
Linked
Data,
and
follow
the
links
to
other
pieces
of
data
that
are
hosted
on
different
sites
across
the
Web.
JSON-LD
is
a
way
of
expressing
Linked
Data
on
the
Web.
The
JSON-LD
data
model
encapsulates
the
following
concepts:
The
JSON-LD
data
model
is
used
to
represent
linked
data
graph
s.
A
linked
data
graph
is
an
unordered
labeled
directed
graph,
where
each
node
is
a
subject
or
object
,
and
edges
are
labeled
using
properties
.
A
subject
is
any
node
in
a
linked
data
graph
with
at
least
one
outgoing
edge.
A
subject
should
</del>
<ins class="diff-chg">JSON
Grammar
</ins>
</em>
<del class="diff-old">be
labeled
with
an
IRI
(an
Internationalized
Resource
Identifier
as
described
</del>
<ins class="diff-chg">section
</ins>
in
[
<cite>
<del class="diff-old">RFC3987
</del>
<a class="bibref" href="#bib-RFC4627">
<ins class="diff-chg">RFC4627
</ins>
</a>
</cite>
<del class="diff-old">]).
An
object
is
a
node
in
a
linked
data
graph
with
at
least
one
incoming
edge.
An
object
may
be
labeled
with
an
IRI
or
a
label
that
is
not
an
IRI
such
as
plain
text,
internationalized
text,
or
a
strictly-typed
data
value.
A
node
may
be
a
subject
and
an
object
at
the
same
time.
A
property
is
the
label
on
an
edge
in
a
linked
data
graph
.
A
property
should
be
an
IRI
.
An
IRI
that
is
a
label
in
a
linked
data
graph
should
be
dereferencable
to
a
Linked
Data
document
describing
the
labeled
subject
,
property
or
object
.
Note
A
Linked
Data
document
does
not
necessarily
need
to
be
expressed
in
JSON-LD.
The
notion
of
Linked
Data
is
a
concept
independent
of
any
given
serialization
format.
Figure
1:
An
example
of
a
linked
data
graph.
There
are
a
number
of
best
practices
that
can
ensure
that
developers
will
generate
good
Linked
Data
</del>
<ins class="diff-chg">]
</ins>
for
<del class="diff-old">the
Web.
JSON-LD
formalizes
those
techniques
by
providing
a
mechanism
to
map
JSON
data,
i.e.,
keys
and
values,
to
IRI
s.
This
does
not
mean
that
JSON-LD
requires
every
key
or
value
to
be
an
IRI
,
but
rather
ensures
that
keys
and
values
can
be
mapped
to
IRIs
if
the
developer
desires
to
transform
their
data
into
Linked
Data
.
3.3
General
Terminology
The
following
is
an
explanation
of
the
general
terminology
used
in
this
document.
Many
of
the
terms
should
be
familiar
to
developers
that
have
used
JSON:
</del>
<ins class="diff-chg">formal
definitions.
</ins>
</p>
<dl>
<dt>
<dfn title="json_object" id="dfn-json_object">
JSON
object
</dfn>
</dt>
<dd>
An
object
structure
is
represented
as
a
pair
of
curly
brackets
surrounding
zero
or
more
key-value
pairs.
A
key
is
a
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>.
A
single
colon
comes
after
each
key,
separating
the
key
from
the
value.
A
single
comma
separates
a
value
from
a
following
key.
<del class="diff-old">The
keys
within
an
object
should
be
unique.
</del>
</dd>
<dt>
<dfn title="array" id="dfn-array">
array
</dfn>
</dt>
<dd>
<del class="diff-old">In
JSON,
an
array
is
an
ordered
sequence
of
zero
or
more
values.
</del>
An
array
<ins class="diff-new">structure
</ins>
is
represented
as
square
brackets
surrounding
zero
or
more
values
<del class="diff-old">that
</del>
<ins class="diff-chg">(or
elements).
Elements
</ins>
are
separated
by
commas.
<ins class="diff-new">In
JSON,
an
array
is
an
</ins><em><ins class="diff-new">
ordered
</ins></em><ins class="diff-new">
sequence
of
zero
or
more
values.
</ins>
While
JSON-LD
uses
the
same
array
representation
as
JSON,
the
collection
is
<em>
unordered
</em>
by
default.
While
order
is
preserved
in
regular
JSON
arrays,
it
is
not
in
regular
JSON-LD
arrays
unless
specific
markup
is
provided
(see
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
</a>
).
</dd>
<dt>
<dfn title="string" id="dfn-string">
string
</dfn>
</dt>
<dd>
A
string
is
a
sequence
of
zero
or
more
Unicode
characters,
wrapped
in
double
quotes,
using
backslash
escapes
(if
necessary).
A
character
is
represented
as
a
single
character
string.
</dd>
<dt>
<dfn title="number" id="dfn-number">
number
</dfn>
</dt>
<dd>
A
number
is
similar
to
that
used
in
most
programming
languages,
except
that
the
octal
and
hexadecimal
formats
are
not
used
and
that
leading
zeros
are
not
allowed.
</dd>
<dt>
<dfn title="true" id="dfn-true">
true
</dfn>
and
<dfn title="false" id="dfn-false">
false
</dfn>
</dt>
<dd>
Values
that
are
used
to
express
one
of
two
possible
boolean
states.
</dd>
<dt>
<dfn title="null" id="dfn-null">
null
</dfn>
</dt>
<dd>
The
<a class="tref internalDFN" title="null" href="#dfn-null">
null
<del class="diff-old">value
is
used
to
make
a
JSON-LD
processor
&quot;forget&quot;
any
previously
defined
JSON
key
that
is
associated
with
the
null
</del>
</a>
value.
<del class="diff-old">If
a
previous
definition
doesn't
exist,
the
entire
</del>
<ins class="diff-chg">A
</ins>
key-value
<del class="diff-old">is
ignored.
If
a
previous
definition
of
</del>
<ins class="diff-chg">pair
in
</ins>
the
<del class="diff-old">key
does
exist,
</del>
<code>
<ins class="diff-chg">@context
</ins></code><ins class="diff-chg">
where
</ins>
the
<del class="diff-old">previous
definition
</del>
<ins class="diff-chg">value,
or
the
</ins><code><ins class="diff-chg">
@id
</ins></code><ins class="diff-chg">
of
the
value,
</ins>
is
<del class="diff-old">undefined.
node
definition
A
JSON
object
</del>
<a class="tref internalDFN" title="null" href="#dfn-null">
<ins class="diff-chg">null
</ins>
</a>
<del class="diff-old">used
to
represent
</del>
<ins class="diff-chg">explicitly
decouples
</ins>
a
<del class="diff-old">node
and
one
or
more
properties
of
that
node.
</del>
<ins class="diff-chg">term's
association
with
an
</ins><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr>.
A
<del class="diff-old">JSON
object
is
</del>
<ins class="diff-chg">key-value
pair
in
the
body
of
</ins>
a
<del class="diff-old">node
definition
</del>
<ins class="diff-chg">JSON-LD
document
whose
value
is
</ins><a class="tref internalDFN" title="null" href="#dfn-null"><ins class="diff-chg">
null
</ins></a><ins class="diff-chg">
has
the
same
meaning
as
</ins>
if
<del class="diff-old">it
does
not
contain
</del>
the
<del class="diff-old">keys
</del>
<ins class="diff-chg">key-value
pair
was
not
defined.
If
</ins>
<code>
@value
</code>,
<code>
@list
</code>,
or
<code>
@set
</code>
<del class="diff-old">and
it
has
one
or
more
keys
other
than
@id
.
A
node
definition
may
be
spread
among
different
parts
of
a
document
or
even
between
different
documents.
node
reference
A
</del>
<ins class="diff-chg">is
set
to
</ins><a class="tref internalDFN" title="null" href="#dfn-null"><ins class="diff-chg">
null
</ins></a><ins class="diff-chg">
in
expanded
form,
then
the
entire
</ins>
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
<del class="diff-old">used
to
refer
to
a
node
that
contains
a
single
key-value
pair
where
the
key
</del>
is
<del class="diff-old">@id
.
</del>
<ins class="diff-chg">ignored.
</ins>
</dd>
</dl>
</section>
<section id="syntax-tokens-and-keywords">
<h3>
<span class="secno">
<del class="diff-old">3.4
</del>
<ins class="diff-chg">3.2
</ins>
</span>
Syntax
Tokens
and
Keywords
</h3>
<p>
JSON-LD
specifies
a
number
of
syntax
tokens
and
<dfn title="keyword" id="dfn-keyword">
keywords
</dfn>
that
are
a
core
part
of
the
language:
</p>
<dl>
<dt>
<code>
@context
</code>
</dt>
<dd>
Used
to
define
the
short-hand
names
that
are
used
throughout
a
JSON-LD
document.
These
short-hand
names
are
called
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
and
help
developers
to
express
specific
identifiers
in
a
compact
manner.
The
<code>
@context
</code>
keyword
is
described
in
detail
in
the
section
titled
<a href="#the-context" class="sec-ref">
<span class="secno">
<del class="diff-old">3.5
</del>
<ins class="diff-chg">5.1
</ins>
</span>
<span class="sec-title">
The
Context
</span>
</a>.
</dd>
<dt>
<code>
<del class="diff-old">@graph
Used
to
explicitly
label
a
linked
data
graph
.
This
keyword
is
described
in
4.11
Named
Graphs
.
</del>
@id
</code>
</dt>
<dd>
Used
to
uniquely
identify
<em>
things
</em>
that
are
being
described
in
the
document.
This
keyword
is
described
in
<a href="#node-identifiers" class="sec-ref">
<span class="secno">
<del class="diff-old">3.8
</del>
<ins class="diff-chg">5.4
</ins>
</span>
<span class="sec-title">
Node
Identifiers
</span>
</a>.
</dd>
<dt>
<code>
@value
</code>
</dt>
<dd>
Used
to
specify
the
data
that
is
associated
with
a
particular
<a class="tref internalDFN" title="property" href="#dfn-property">
property
</a>
in
the
graph.
This
keyword
is
described
in
<a href="#string-internationalization" class="sec-ref">
<span class="secno">
<del class="diff-old">3.10
</del>
<ins class="diff-chg">5.6
</ins>
</span>
<span class="sec-title">
String
Internationalization
</span>
</a>
and
<a href="#typed-values" class="sec-ref">
<span class="secno">
<del class="diff-old">4.2
</del>
<ins class="diff-chg">6.2
</ins>
</span>
<span class="sec-title">
Typed
Values
</span>
</a>.
</dd>
<dt>
<code>
@language
</code>
</dt>
<dd>
Used
to
specify
the
native
language
for
a
particular
value
or
the
default
language
of
a
JSON-LD
document.
This
keyword
is
described
in
the
section
titled
<a href="#string-internationalization" class="sec-ref">
<span class="secno">
<del class="diff-old">3.10
</del>
<ins class="diff-chg">5.6
</ins>
</span>
<span class="sec-title">
String
Internationalization
</span>
</a>.
</dd>
<dt>
<code>
@type
</code>
</dt>
<dd>
Used
to
set
the
data
type
of
a
<a class="tref internalDFN" title="node" href="#dfn-node">
node
</a>
or
<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
typed
value
</a>.
This
keyword
is
described
in
the
section
titled
<a href="#typed-values" class="sec-ref">
<span class="secno">
<del class="diff-old">4.2
</del>
<ins class="diff-chg">6.2
</ins>
</span>
<span class="sec-title">
Typed
Values
</span>
</a>.
</dd>
<dt>
<code>
@container
</code>
</dt>
<dd>
Used
to
set
the
container
of
a
particular
value.
This
keyword
is
described
in
the
section
titled
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
</a>.
</dd>
<dt>
<code>
@list
</code>
</dt>
<dd>
Used
to
express
an
ordered
set
of
data.
This
keyword
is
described
in
the
section
titled
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
</a>.
</dd>
<dt>
<code>
@set
</code>
</dt>
<dd>
Used
to
express
an
unordered
set
of
<del class="diff-old">data.
</del>
<ins class="diff-chg">data
and
to
ensure
that
values
are
always
represented
as
arrays.
</ins>
This
keyword
is
described
in
the
section
titled
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
</a>.
</dd>
<dt>
<code>
<del class="diff-old">@vocab
</del>
<ins class="diff-chg">@annotation
</ins>
</code>
</dt>
<dd>
Used
to
<del class="diff-old">set
</del>
<ins class="diff-chg">specify
that
a
container
is
used
to
index
information
and
that
processing
should
continue
deeper
into
a
JSON
data
structure.
This
keyword
is
described
in
</ins>
the
<del class="diff-old">base
</del>
<ins class="diff-chg">section
titled
</ins><a href="#data-annotations" class="sec-ref"><span class="secno"><ins class="diff-chg">
6.14
</ins></span><span class="sec-title"><ins class="diff-chg">
Data
Annotations
</ins></span></a>.</dd><dt><code><ins class="diff-chg">
@vocab
</ins></code></dt><dd><ins class="diff-chg">
Used
to
expand
properties
and
values
in
</ins><code><ins class="diff-chg">
@type
</ins></code><ins class="diff-chg">
with
a
common
prefix
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">for
all
property
IRIs
affected
by
the
active
context
</del>
</a>.
This
keyword
is
described
in
section
<a href="#iris" class="sec-ref">
<span class="secno">
<del class="diff-old">3.7
</del>
<ins class="diff-chg">5.3
</ins>
</span>
<span class="sec-title">
IRIs
</span>
</a>.
</dd>
<dt>
<code>
<ins class="diff-new">@graph
</ins></code></dt><dd><ins class="diff-new">
Used
to
explicitly
label
a
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-new">
JSON-LD
graph
</ins></a>.<ins class="diff-new">
This
keyword
is
described
in
</ins><a href="#named-graphs" class="sec-ref"><span class="secno"><ins class="diff-new">
6.11
</ins></span><span class="sec-title"><ins class="diff-new">
Named
Graphs
</ins></span></a>.</dd><dt>
<code>:
</code>
</dt>
<dd>
The
separator
for
JSON
keys
and
values
that
use
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
IRIs
</a>.
</dd>
</dl>
<p>
For
the
avoidance
of
doubt,
all
keys,
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keywords
</a>,
and
values
in
JSON-LD
are
case-sensitive.
</p>
</section>
</section>
<section class="normative" id="conformance">
<h2>
<span class="secno">
<ins class="diff-new">4.
</ins></span><ins class="diff-new">
Conformance
</ins></h2><p><ins class="diff-new">
The
JSON-LD
Syntax
specification
describes
the
conformance
criteria
for
JSON-LD
documents
(relevant
to
authors
and
authoring
tool
implementors).
</ins></p><p><ins class="diff-new">
A
</ins><a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document"><ins class="diff-new">
JSON-LD
document
</ins></a><ins class="diff-new">
complies
with
this
specification
if
it
follows
the
normative
statements
for
documents
defined
in
sections
</ins><a href="#referencing-contexts-from-json-documents" class="sec-ref"><span class="secno"><ins class="diff-new">
6.4
</ins></span><span class="sec-title"><ins class="diff-new">
Referencing
Contexts
from
JSON
Documents
</ins></span></a><ins class="diff-new">
and
</ins><a href="#json-ld-grammar" class="sec-ref"><span class="secno"><ins class="diff-new">
B.
</ins></span><span class="sec-title"><ins class="diff-new">
JSON-LD
Grammar
</ins></span></a>.<ins class="diff-new">
For
convenience,
normative
statements
for
documents
are
often
phrased
as
statements
on
the
properties
of
the
document.
</ins></p><p><ins class="diff-new">
The
key
words
</ins><em class="rfc2119" title="must"><ins class="diff-new">
must
</ins></em>,<em class="rfc2119" title="must not"><ins class="diff-new">
must
not
</ins></em>,<em class="rfc2119" title="required"><ins class="diff-new">
required
</ins></em>,<em class="rfc2119" title="shall"><ins class="diff-new">
shall
</ins></em>,<em class="rfc2119" title="shall not"><ins class="diff-new">
shall
not
</ins></em>,<em class="rfc2119" title="should"><ins class="diff-new">
should
</ins></em>,<em class="rfc2119" title="should not"><ins class="diff-new">
should
not
</ins></em>,<em class="rfc2119" title="recommended"><ins class="diff-new">
recommended
</ins></em>,<em class="rfc2119" title="not recommended"><ins class="diff-new">
not
recommended
</ins></em>,<em class="rfc2119" title="may"><ins class="diff-new">
may
</ins></em>,<ins class="diff-new">
and
</ins><em class="rfc2119" title="optional"><ins class="diff-new">
optional
</ins></em><ins class="diff-new">
in
this
Recommendation
have
the
meaning
defined
in
[
</ins><cite><a class="bibref" href="#bib-RFC2119"><ins class="diff-new">
RFC2119
</ins></a></cite><ins class="diff-new">
].
</ins></p></section><section class="normative" id="basic-concepts"><h2><span class="secno"><ins class="diff-new">
5.
</ins></span><ins class="diff-new">
Basic
Concepts
</ins></h2>
<section id="the-context">
<h3>
<span class="secno">
<del class="diff-old">3.5
</del>
<ins class="diff-chg">5.1
</ins>
</span>
The
Context
</h3>
<p>
In
JSON-LD,
a
<dfn title="context" id="dfn-context">
context
</dfn>
is
used
to
map
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
s,
</del>
<ins class="diff-chg">terms
</ins></a>,
i.e.,
properties
with
associated
values
in
an
JSON
document,
to
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
s.
A
term
is
a
short
word
that
expands
to
an
IRI
.
Term
s
may
be
defined
as
any
valid
JSON
string
other
than
a
JSON-LD
keyword
</del>
<ins class="diff-chg">IRIs
</ins>
</a>.
<del class="diff-old">To
avoid
forward-compatibility
issues,
term
s
starting
with
an
@
character
should
not
be
used
as
they
might
be
used
as
keywords
in
future
versions
of
JSON-LD.
Furthermore,
the
use
of
empty
terms
(
&quot;&quot;
)
is
discouraged
as
not
all
programming
languages
are
able
to
handle
empty
property
names.
</del>
</p>
<p>
The
Web
uses
<a class="tref internalDFN" title="iri" href="#dfn-iri">
IRIs
</a>
for
unambiguous
identification.
The
idea
is
that
these
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
mean
something
that
may
be
of
use
to
other
developers
and
that
it
is
useful
to
give
them
an
unambiguous
identifier.
That
is,
it
is
useful
for
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
to
expand
to
IRIs
so
that
developers
don't
accidentally
step
on
each
other's
<dfn title="vocabulary" id="dfn-vocabulary">
vocabulary
</dfn>
terms
and
other
resources.
Furthermore,
developers,
and
machines,
are
able
to
use
this
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
(by
plugging
it
directly
into
a
web
browser,
for
instance)
to
go
to
the
term
and
get
a
definition
of
what
the
term
means.
This
mechanism
is
analogous
to
the
way
we
can
use
<a href="http://wordnet.princeton.edu/">
WordNet
</a>
today
to
see
the
definition
of
words
in
the
English
language.
Developers
and
machines
need
the
same
sort
of
definition
of
terms.
<a class="tref internalDFN" title="iri" href="#dfn-iri">
IRIs
</a>
provide
a
way
to
ensure
that
these
terms
are
unambiguous.
For
example,
the
term
<code>
name
</code>
may
map
directly
to
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<code>
http://xmlns.com/foaf/0.1/name
</code>.
This
allows
JSON-LD
documents
to
be
constructed
using
the
common
JSON
practice
of
simple
key-value
pairs
while
ensuring
that
the
data
is
useful
outside
of
the
page,
API
or
database
in
which
it
resides.
<del class="diff-old">The
value
of
a
term
mapping
must
be
either;
1)
a
simple
string
</del>
</p>
<p>
<ins class="diff-chg">Note
that,
to
avoid
forward-compatibility
issues,
terms
starting
</ins>
with
<ins class="diff-new">an
</ins><code><ins class="diff-new">
@
</ins></code><ins class="diff-new">
character
are
to
be
avoided
as
they
might
be
used
as
keywords
in
future
versions
of
JSON-LD.
Furthermore,
</ins>
the
<del class="diff-old">lexical
form
</del>
<ins class="diff-chg">use
</ins>
of
<del class="diff-old">an
absolute
IRI
or
2)
compact
IRI
,
or
3)
an
JSON
object
</del>
<ins class="diff-chg">empty
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
terms
</ins>
</a>
<del class="diff-old">containing
an
@id
,
@type
,
@language
,
or
</del>
<ins class="diff-chg">(
</ins>
<code>
<del class="diff-old">@container
</del>
<ins class="diff-chg">&quot;&quot;
</ins>
</code>
<del class="diff-old">keyword
(all
other
keywords
</del>
<ins class="diff-chg">)
is
discouraged
as
not
all
programming
languages
</ins>
are
<del class="diff-old">ignored
by
a
JSON-LD
processor).
</del>
<ins class="diff-chg">able
to
handle
empty
property
names.
</ins>
</p>
<p>
<del class="diff-old">These
Linked
Data
</del>
<ins class="diff-chg">In
a
JSON-LD
document,
the
mapping
between
</ins>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
are
</del>
<ins class="diff-chg">and
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a><ins class="diff-chg">
is
</ins>
typically
collected
in
a
<a class="tref internalDFN" title="context_definition" href="#dfn-context_definition">
context
<del class="diff-old">document
</del>
<ins class="diff-chg">definition
</ins></a>
that
would
look
something
like
this:
</p>
<div class="example"><div class="example-title"><span>Example 1</span>: Context definition</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;depiction&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    },
    &quot;homepage&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    },
  }
}
</pre>
</div>
<p>
Let's
assume
that
a
developer
starts
with
the
following
JSON
document:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 2</span>: Sample JSON document</div><pre class="example">{
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</pre>
</div>
<p>
The
developer
can
add
a
single
line
to
the
JSON
document
above
to
reference
the
context
and
transform
it
into
a
JSON-LD
document:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 3</span>: Referencing a JSON-LD context</div><pre class="example">{
  <span class="diff">&quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,</span>
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</pre>
</div>
<p>
The
additions
above
transform
the
previous
JSON
document
into
a
JSON
document
with
added
semantics
because
the
<code>
@context
</code>
specifies
how
the
<strong>
name
</strong>,
<strong>
homepage
</strong>,
and
<strong>
depiction
</strong>
terms
map
to
<a class="tref internalDFN" title="iri" href="#dfn-iri">
IRIs
</a>.
Mapping
those
keys
to
IRIs
gives
the
data
global
context.
If
two
developers
use
the
same
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
to
describe
a
property,
they
are
more
than
likely
expressing
the
same
concept.
This
allows
both
developers
to
re-use
each
others'
data
without
having
to
agree
to
how
their
data
will
interoperate
on
a
site-by-site
basis.
Contexts
may
also
contain
<del class="diff-old">type
</del>
<ins class="diff-chg">type,
language
or
additional
</ins>
information
for
certain
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
s
as
well
as
other
processing
instructions
for
the
JSON-LD
processor.
</del>
<ins class="diff-chg">terms
</ins></a>.
</p>
<del class="diff-old">Note
</del>
<p>
External
JSON-LD
context
documents
may
contain
extra
information
located
outside
of
the
<code>
@context
</code>
key,
such
as
documentation
about
the
<a class="tref internalDFN" title="term" href="#dfn-term">
terms
</a>
declared
in
the
document.
<del class="diff-old">When
importing
a
@context
value
from
an
external
JSON-LD
context
document,
any
extra
information
</del>
<ins class="diff-chg">Information
</ins>
contained
outside
of
the
<code>
@context
</code>
value
<del class="diff-old">must
be
discarded.
</del>
<ins class="diff-chg">is
simply
discarded
when
the
document
is
used
as
an
external
JSON-LD
context
document
(see
</ins><a href="#referencing-contexts-from-json-documents" class="sec-ref">
<span class="secno">
<ins class="diff-chg">6.4
</ins></span><span class="sec-title"><ins class="diff-chg">
Referencing
Contexts
from
JSON
Documents
</ins></span></a><ins class="diff-chg">
).
</ins></p>
<p>
Contexts
may
<ins class="diff-chg">also
</ins>
be
specified
in-line.
This
ensures
that
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
documents
</a>
can
be
<del class="diff-old">processed
when
</del>
<ins class="diff-chg">understood
even
in
the
absence
of
</ins>
a
<del class="diff-old">JSON-LD
processor
does
not
have
access
</del>
<ins class="diff-chg">connection
</ins>
to
the
Web.
</p>
<div class="example"><div class="example-title"><span>Example 4</span>: In-line context definition</div><pre class="example">{
  <span class="diff">&quot;@context&quot;:
  {
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;depiction&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    },
    &quot;homepage&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    },
  },</span>
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</pre>
</div>
<p>
Contexts
may
be
used
at
any
time
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
is
defined.
<del class="diff-old">A
node
definition
</del>
<ins class="diff-chg">In
particular,
a
</ins><a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document"><ins class="diff-chg">
JSON-LD
document
</ins>
</a>
may
<del class="diff-old">specify
multiple
contexts,
using
an
array
,
which
is
processed
</del>
<ins class="diff-chg">define
more
than
one
context,
as
</ins>
in
<del class="diff-old">order.
</del>
<ins class="diff-chg">the
following
example:
</ins></p><div class="example"><div class="example-title"><span>Example 5</span>: Multiple separate contexts</div><pre class="example">[<ins class="diff-chg">
  {
</ins>    <span class="diff">&quot;@context&quot;: &quot;http://example.org/contexts/person.jsonld&quot;,</span><ins class="diff-chg">
    &quot;name&quot;: &quot;Manu Sporny&quot;,
    &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
    &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
  },
  {
</ins>    <span class="diff">&quot;@context&quot;: &quot;http://example.org/contexts/place.jsonld&quot;,</span><ins class="diff-chg">
    &quot;name&quot;: &quot;The Empire State Building&quot;,
    &quot;description&quot;: &quot;The Empire State Building is a 102-story landmark in New York City.&quot;,
    &quot;geo&quot;: {
      &quot;latitude&quot;: &quot;40.75&quot;,
      &quot;longitude&quot;: &quot;73.98&quot;
    }
  }
]
</ins></pre></div><p>
This
is
useful
when
an
author
would
like
to
use
an
existing
context
and
add
application-specific
terms
to
the
existing
context.
Duplicate
context
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
must
be
</del>
<ins class="diff-chg">are
</ins>
overridden
using
a
last-defined-overrides
mechanism.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 6</span>: Scoped contexts within node objects</div><pre class="example">{
  <span class="diff">&quot;@context&quot;:
  {
    &quot;name&quot;: &quot;http://example.com/person#name&quot;,
    &quot;details&quot;: &quot;http://example.com/person#details&quot;
  },</span>
  &quot;<span class="diff">name</span>&quot;: &quot;Markus Lanthaler&quot;,
  ...
  &quot;details&quot;:
  {
    <span class="diff">&quot;@context&quot;: {
      &quot;name&quot;: &quot;http://example.com/organization#name&quot;
    },</span>
    &quot;<span class="diff">name</span>&quot;: &quot;Graz University of Technology&quot;
  }
}
</pre>
</div>
<p>
In
the
example
above,
the
<code>
name
</code>
prefix
is
overridden
in
the
more
deeply
nested
<code>
details
</code>
structure.
Note
that
this
is
rarely
a
good
authoring
practice
and
is
typically
used
when
there
exist
legacy
applications
that
depend
on
the
specific
structure
of
the
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>.
<del class="diff-old">Note
</del>
If
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
is
re-defined
within
a
context,
all
previous
rules
associated
with
the
previous
definition
are
removed.
<del class="diff-old">A
</del>
<ins class="diff-chg">If
that
</ins>
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
<del class="diff-old">defined
in
a
previous
context
must
be
removed,
if
it
</del>
is
re-defined
to
<code>
null
<del class="diff-old">.
</del>
</code>,
<ins class="diff-chg">the
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
term
</ins></a><ins class="diff-chg">
is
effectively
removed
from
the
list
of
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
terms
</ins></a><ins class="diff-chg">
defined
in
the
</ins><a class="tref internalDFN" title="active_context" href="#dfn-active_context"><ins class="diff-chg">
active
context
</ins></a>.
</p>
<p>
<ins class="diff-new">A
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a><ins class="diff-new">
may
specify
multiple
contexts,
using
an
</ins><a class="tref internalDFN" title="array" href="#dfn-array"><ins class="diff-new">
array
</ins></a>,<ins class="diff-new">
processed
in
order.
</ins>
The
set
of
contexts
defined
within
a
specific
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
are
referred
to
as
<dfn title="local_context" id="dfn-local_context">
local
<del class="diff-old">context
s.
</del>
<ins class="diff-chg">contexts
</ins></dfn>.
Setting
the
context
to
<code>
null
</code>
effectively
resets
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>
to
an
empty
context.
The
<dfn title="active_context" id="dfn-active_context">
active
context
</dfn>
refers
to
the
accumulation
of
<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
local
<del class="diff-old">context
</del>
<ins class="diff-chg">contexts
</ins>
</a>
<del class="diff-old">s
</del>
that
are
in
scope
at
a
specific
point
within
the
document.
The
following
example
specifies
an
external
context
and
then
layers
a
local
context
on
top
of
the
external
context:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 7</span>: Combining external and local contexts</div><pre class="example">{
  <span class="diff">&quot;@context&quot;: [
    &quot;http://json-ld.org/contexts/person.jsonld&quot;,
    {
      &quot;pic&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;
    }
  ],</span>
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  <span class="diff">&quot;pic&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;</span>
}
</pre>
</div>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
To
ensure
the
best
possible
performance,
it
is
a
best
practice
to
put
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
definition
at
the
top
of
the
JSON-LD
document.
If
it
isn't
listed
first,
processors
have
to
save
each
key-value
pair
until
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
is
processed.
This
creates
a
memory
and
complexity
burden
for
certain
types
of
low-memory
footprint
JSON-LD
processors.
</p>
</div>
<del class="diff-old">Note
The
null
value
is
processed
in
a
special
way
in
JSON-LD.
Unless
otherwise
specified,
a
JSON-LD
processor
must
act
as
if
a
key-value
pair
in
the
body
of
a
JSON-LD
document
was
never
declared
when
the
value
equals
null
.
If
@value
,
@list
,
or
@set
is
set
to
null
in
expanded
form,
then
the
entire
JSON
object
is
ignored.
If
@context
is
set
to
null
,
the
active
context
is
reset
and
when
used
within
a
context
,
it
removes
any
definition
associated
with
the
key,
unless
otherwise
specified.
</del>
</section>
<section id="from-json-to-json-ld">
<h3>
<span class="secno">
<del class="diff-old">3.6
</del>
<ins class="diff-chg">5.2
</ins>
</span>
From
JSON
to
JSON-LD
</h3>
<p>
If
a
set
of
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
such
as,
<strong>
name
</strong>,
<strong>
homepage
</strong>,
and
<strong>
depiction
</strong>,
are
defined
in
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>,
and
that
context
is
used
to
resolve
the
names
in
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
objects
</a>,
machines
are
able
to
automatically
expand
the
terms
to
something
<del class="diff-old">meaningful
and
unambiguous,
</del>
<ins class="diff-chg">unambiguous
</ins>
like
this:
</p>
<del class="diff-old">{
</del>
  <div class="example"><div class="example-title"><span>Example 8</span>: Expanded terms</div><pre class="example">{
  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
  &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;: &quot;http://manu.sporny.org&quot;
  &quot;<span class="diff">http://xmlns.com/foaf/0.1/depiction</span>&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</pre>
</div>
<p>
Doing
this
allows
JSON
to
be
unambiguously
machine-readable
without
requiring
developers
to
drastically
change
their
workflow.
<ins class="diff-new">A
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-new">
JSON
object
</ins></a><ins class="diff-new">
used
to
define
property
values
of
a
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-new">
node
</ins></a><ins class="diff-new">
is
called
a
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a>.
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
The
example
above
does
not
use
the
<code>
@id
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
to
identify
the
node
being
described
above.
This
type
of
node
is
called
<del class="diff-old">an
unlabeled
</del>
<ins class="diff-chg">a
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
</ins>
node
</a>.
It
is
advised
that
all
<del class="diff-old">nodes
described
</del>
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
<ins class="diff-chg">node
objects
</ins></a>
in
JSON-LD
are
<del class="diff-old">given
unique
identifiers
</del>
<ins class="diff-chg">identified
by
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a>
via
the
<code>
@id
</code>
keyword
unless
the
data
is
not
intended
to
be
linked
to
from
other
data
sets.
</p>
</div>
<del class="diff-old">A
JSON
object
used
to
define
property
values
is
called
a
node
definition
.
Node
definitions
do
not
require
an
@id
.
Node
definitions
that
do
not
contain
an
@id
are
known
as
an
unlabeled
nodes
.
</del>
</section>
<section id="iris">
<h3>
<span class="secno">
<del class="diff-old">3.7
</del>
<ins class="diff-chg">5.3
</ins>
</span>
IRIs
</h3>
<p>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
IRIs
</a>
<ins class="diff-new">(Internationalized
Resource
Identifiers)
</ins>
are
fundamental
to
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
Linked
Data
</a>
as
that
is
how
most
<a class="tref internalDFN" title="node" href="#dfn-node">
nodes
</a>
<del class="diff-old">s
</del>
and
<del class="diff-old">all
</del>
<a class="tref internalDFN" title="property" href="#dfn-property">
properties
</a>
are
identified.
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">s
</del>
can
be
expressed
in
a
variety
of
different
ways
in
<del class="diff-old">JSON-LD.
An
IRI
(an
Internationalized
Resource
Identifier)
is
described
in
[
RFC3987
])
and
the
use
with
JSON-LD
conforms
to
the
definition
of
IRI
in
[
RDF-CONCEPTS
].
</del>
<ins class="diff-chg">JSON-LD:
</ins>
</p>
<ol>
<li>
Except
within
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
definition,
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
in
the
key
position
in
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
that
have
a
mapping
<del class="diff-old">or
a
vocabulary
base
</del>
<ins class="diff-chg">in
the
</ins><a class="tref internalDFN" title="active_context" href="#dfn-active_context"><ins class="diff-chg">
active
context
</ins></a><ins class="diff-chg">
expand
to
an
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
<ins class="diff-chg">If
there's
a
</ins><code><ins class="diff-chg">
@vocab
</ins></code><ins class="diff-chg">
mapping
</ins>
in
the
active
context
<ins class="diff-new">also
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
terms
</ins>
</a>
<ins class="diff-new">without
an
explicit
mapping
in
the
active
context
</ins>
are
expanded
to
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">by
JSON-LD
processors.
</del>
</a>.
</li>
<li>
An
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
is
generated
for
the
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>
value
specified
using
<code>
@id
</code>
or
<code>
@type
</code>.
</li>
<li>
An
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
is
generated
for
the
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>
value
of
any
key
for
which
there
are
<a class="tref internalDFN" title="coercion" href="#dfn-coercion">
coercion
</a>
rules
in
effect
that
identify
the
value
as
an
<code>
@id
</code>.
</li>
</ol>
<p>
IRIs
may
be
represented
as
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">,
</del>
</a>
<ins class="diff-chg">or
</ins>
a
<a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">
relative
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">,
a
term
,
a
compact
IRI
,
or
as
a
value
relative
to
@vocab
.
</del>
</a>.
</p>
<p>
An
<dfn title="absolute_iri" id="dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</dfn>
is
defined
in
[
<cite>
<a class="bibref" href="#bib-RFC3987">
RFC3987
</a>
</cite>
]
containing
a
<em>
scheme
</em>
along
with
<em>
path
</em>
and
optional
<em>
query
</em>
and
<em>
fragment
</em>
segments.
A
<dfn title="relative_iri" id="dfn-relative_iri">
relative
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</dfn>
is
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
that
is
relative
to
some
other
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
In
JSON-LD
all
<a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">
relative
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">s
</del>
are
resolved
relative
to
the
<dfn title="base_iri" id="dfn-base_iri">
base
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</dfn>
associated
with
the
document
(typically,
the
directory
that
contains
the
document
or
the
document
itself).
</p>
<p>
IRIs
can
be
expressed
directly
in
the
key
position
like
so:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 9</span>: IRI as a key</div><pre class="example">{
...
  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
...
}
</pre>
</div>
<p>
In
the
example
above,
the
key
<code>
http://xmlns.com/foaf/0.1/name
</code>
is
interpreted
as
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
because
it
contains
a
colon
(
<code>:
</code>
)
and
the
'http'
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
prefix
</a>
does
not
exist
in
the
context.
</p>
<p>
Term
expansion
occurs
for
IRIs
if
the
value
matches
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
defined
within
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 10</span>: Term expansion from context definition</div><pre class="example">{
  &quot;<span class="diff">@context</span>&quot;:
  {
    &quot;<span class="diff">name</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;
...
  },
  &quot;<span class="diff">name</span>&quot;: &quot;Manu Sporny&quot;,
  &quot;status&quot;: &quot;trollin'&quot;,
...
}
</pre>
</div>
<p>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">Term
</del>
<ins class="diff-chg">Terms
</ins>
</a>
<del class="diff-old">s
</del>
are
case
<del class="diff-old">sensitive,
and
must
be
matched
using
a
case-sensitive
comparison.
</del>
<ins class="diff-chg">sensitive.
</ins>
</p>
<p>
JSON
keys
that
do
not
expand
to
an
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
are
ignored,
or
removed
in
some
cases,
by
the
[
<cite>
<a class="bibref" href="#bib-JSON-LD-API">
JSON-LD-API
</a>
</cite>
].
However,
JSON
keys
that
do
not
include
a
mapping
in
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
are
still
considered
valid
expressions
in
JSON-LD
documents
-
the
keys
just
don't
<del class="diff-old">have
any
machine-readable,
semantic
meaning.
</del>
<ins class="diff-chg">expand
to
unambiguous
identifiers.
</ins>
</p>
<p>
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
<del class="diff-old">Prefix
</del>
<ins class="diff-chg">Prefixes
</ins>
</a>
<del class="diff-old">es
</del>
are
expanded
when
the
form
of
the
value
is
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
represented
as
a
<code>
prefix:suffix
</code>
combination,
and
the
prefix
matches
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
defined
within
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 11</span>: Prefix expansion</div><pre class="example">{
  &quot;<span class="diff">@context</span>&quot;:
  {
    &quot;<span class="diff">foaf</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/</span>&quot;
...
  },
  &quot;<span class="diff">foaf:name</span>&quot;: &quot;Manu Sporny&quot;,
...
}
</pre>
</div>
<p>
<code>
foaf:name
</code>
above
will
automatically
expand
out
to
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<code>
http://xmlns.com/foaf/0.1/name
</code>.
See
<a href="#compact-iris" class="sec-ref">
<span class="secno">
<del class="diff-old">4.1
</del>
<ins class="diff-chg">6.1
</ins>
</span>
<span class="sec-title">
Compact
IRIs
</span>
</a>
for
more
details.
</p>
<p>
<del class="diff-old">If
the
@vocab
is
set,
all
keys
that
do
not
match
a
term
or
a
prefix
are
</del>
It
is
often
common
that
all
types
and
properties
come
from
the
same
vocabulary.
JSON-LD's
<code>
@vocab
</code>
keyword
allows
to
set
a
<del class="diff-old">base
IRI
</del>
<ins class="diff-chg">common
prefix
</ins>
to
be
used
for
all
properties
and
types
that
<del class="diff-old">that
do
not
</del>
<ins class="diff-chg">neither
</ins>
match
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
<del class="diff-old">,
</del>
</a>
<ins class="diff-chg">nor
</ins>
a
<del class="diff-old">prefix
,
</del>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
<ins class="diff-chg">compact
</ins><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a>
or
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
(i.e.,
do
not
contain
a
colon).
<del class="diff-old">The
@vocab
mapping
must
have
a
value
of
a
simple
string
with
the
lexical
form
of
an
absolute
IRI
.
</del>
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 12</span>: Using a common vocabulary prefix</div><pre class="example">{
  <span class="diff">&quot;@context&quot;: {
    &quot;@vocab&quot;: &quot;http://xmlns.com/foaf/1.0/&quot;
  },</span>
  &quot;@type&quot;: <span class="diff">&quot;Person&quot;</span>,
  <span class="diff">&quot;name&quot;</span>: &quot;Manu Sporny&quot;,
}
</pre>
</div>
<p>
An
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
is
generated
when
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
is
used
in
the
value
position
that
contains
an
<code>
@id
</code>
keyword:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 13</span>: Expanded IRI definition</div><pre class="example">{
...
  &quot;homepage&quot;: { &quot;<span class="diff">@id</span>&quot;: &quot;http://manu.sporny.org&quot; }
...
}
</pre>
</div>
<del class="diff-old">Note
</del>
<p>
Specifying
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
with
an
<code>
@id
</code>
key
is
used
to
identify
that
<a class="tref internalDFN" title="node" href="#dfn-node">
node
</a>
using
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
When
the
object
has
only
the
<code>
@id
</code>,
it
is
called
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">reference
</del>
<ins class="diff-chg">object
</ins>
</a>.
This
facility
may
also
be
used
to
link
to
another
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
using
a
mechanism
called
<a class="tref internalDFN" title="embedding" href="#dfn-embedding">
embedding
</a>,
which
is
covered
in
the
section
titled
<a href="#embedding" class="sec-ref">
<span class="secno">
<del class="diff-old">4.10
</del>
<ins class="diff-chg">6.10
</ins>
</span>
<span class="sec-title">
Embedding
</span>
</a>.
</p>
<p>
If
type
<a class="tref internalDFN" title="coercion" href="#dfn-coercion">
coercion
</a>
rules
are
specified
in
the
<code>
@context
</code>
for
a
particular
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
or
property
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>,
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
is
generated:
</p>
<div class="example"><div class="example-title"><span>Example 14</span>: Type coercion</div><pre class="example">{<span class="diff">
  &quot;@context&quot;:
  {
    ...
    &quot;homepage&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    }
    ...
  }</span>
...
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
...
}
</pre>
</div>
<p>
In
the
example
above,
even
though
the
value
<code>
http://manu.sporny.org/
</code>
is
expressed
as
a
JSON
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
the
type
<a class="tref internalDFN" title="coercion" href="#dfn-coercion">
coercion
</a>
rules
will
transform
the
value
into
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
when
<del class="diff-old">processed
by
a
</del>
<ins class="diff-chg">generating
the
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph">
JSON-LD
<del class="diff-old">Processor.
</del>
<ins class="diff-chg">graph
</ins></a>.
</p>
</section>
<section id="node-identifiers">
<h3>
<span class="secno">
<del class="diff-old">3.8
</del>
<ins class="diff-chg">5.4
</ins>
</span>
Node
Identifiers
</h3>
<p>
To
be
able
to
externally
reference
nodes
in
a
graph,
it
is
important
that
each
<a class="tref internalDFN" title="node" href="#dfn-node">
node
</a>
has
an
unambiguous
identifier.
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">s
</del>
are
a
fundamental
concept
of
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
Linked
Data
</a>,
and
nodes
should
have
a
de-referencable
identifier
used
to
name
and
locate
them.
For
nodes
to
be
truly
linked,
de-referencing
the
identifier
should
result
in
a
representation
of
that
node
(for
example,
using
a
URL
to
retrieve
a
web
page).
Associating
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
with
a
node
tells
an
application
that
the
returned
document
contains
a
description
of
the
node
requested.
</p>
<p>
JSON-LD
documents
may
also
contain
descriptions
of
other
nodes,
so
it
is
necessary
to
be
able
to
uniquely
identify
each
node
which
may
be
externally
referenced.
</p>
<p>
The
node
of
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
is
identified
using
the
<code>
@id
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 15</span>: Identifying a node</div><pre class="example">{
  &quot;@context&quot;:
  {
    ...
    &quot;homepage&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    }
    ...
  },
  &quot;<span class="diff">@id</span>&quot;: &quot;<span class="diff">http://example.org/people#joebob</span>&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
...
}
</pre>
</div>
<p>
The
example
above
contains
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<ins class="diff-new">object
</ins></a>
identified
by
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<code>
http://example.org/people#joebob
</code>.
</p>
<p>
<del class="diff-old">A
JSON
object
used
to
define
property
values
is
called
a
node
definition
.
Node
definitions
do
not
require
an
@id
.
A
node
definition
that
does
not
contain
an
@id
property
defines
properties
of
an
unlabeled
</del>
<ins class="diff-chg">Once
defined,
the
</ins><a class="tref internalDFN" title="node" href="#dfn-node">
node
<del class="diff-old">.
Node
definitions
</del>
</a>
<del class="diff-old">may
</del>
<ins class="diff-chg">'s
unique
identifier
can
</ins>
be
<del class="diff-old">spread
among
different
</del>
<ins class="diff-chg">used
to
refer
to
it
from
other
</ins>
parts
of
<del class="diff-old">a
</del>
<ins class="diff-chg">the
</ins>
document
or
<del class="diff-old">even
between
different
documents.
Note
To
ensure
the
best
possible
performance,
when
possible,
it
is
a
best
practice
to
put
JSON-LD
keyword
s,
such
as
@id
and
@context
before
other
key-value
pairs
in
a
JSON
object
.
However,
keys
in
</del>
<ins class="diff-chg">from
external
documents,
using
</ins>
a
<del class="diff-old">JSON
</del>
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
<ins class="diff-chg">node
</ins>
object
</a>
<del class="diff-old">are
not
ordered,
so
processors
must
not
depend
on
key
ordering.
If
keywords
are
not
listed
first,
processors
have
to
save
each
key-value
pair
until
at
least
the
@context
and
the
</del>
<ins class="diff-chg">that
only
contains
an
</ins>
<code>
@id
</code>
<del class="diff-old">are
processed.
Not
specifying
those
keywords
first
creates
a
memory
and
complexity
burden
for
low-memory
footprint
processors,
forcing
them
to
use
more
memory
and
computing
cycles
than
necessary.
</del>
<ins class="diff-chg">key:
</ins>
</p>
<div class="example"><div class="example-title"><span>Example 16</span>: Referencing a node using its unique identifier</div><pre class="example">{
<ins class="diff-new">  &quot;@context&quot;: ...,
  &quot;@graph&quot;: [
    {
      &quot;@id&quot;: &quot;http://example.org/library&quot;,
      &quot;@type&quot;: &quot;ex:Library&quot;,
</ins>      <span class="diff">&quot;ex:contains&quot;: {&quot;@id&quot;: &quot;http://example.org/library/the-republic&quot;}</span><ins class="diff-new">
    }, {
      &quot;@id&quot;: &quot;http://example.org/library/the-republic&quot;,
      &quot;@type&quot;: &quot;ex:Book&quot;,
      &quot;dc:creator&quot;: &quot;Plato&quot;,
      &quot;dc:title&quot;: &quot;The Republic&quot;,
</ins>      <span class="diff">&quot;ex:contains&quot;: {&quot;@id&quot;: &quot;http://example.org/library/the-republic#introduction&quot;}</span><ins class="diff-new">
    }, {
      &quot;@id&quot;: &quot;http://example.org/library/the-republic#introduction&quot;,
      &quot;@type&quot;: &quot;ex:Chapter&quot;,
      &quot;dc:description&quot;: &quot;An introductory chapter on The Republic.&quot;,
      &quot;dc:title&quot;: &quot;The Introduction&quot;
    }
  ]
}
}
</ins></pre>
</div>
</section>
<section id="specifying-the-type">
<h3>
<span class="secno">
<del class="diff-old">3.9
</del>
<ins class="diff-chg">5.5
</ins>
</span>
Specifying
the
Type
</h3>
<p>
The
type
of
a
particular
node
can
be
specified
using
the
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>.
<del class="diff-old">To
be
considered
</del>
<ins class="diff-chg">In
</ins>
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
Linked
Data
</a>,
types
<del class="diff-old">must
be
</del>
<ins class="diff-chg">are
</ins>
uniquely
identified
<del class="diff-old">by
</del>
<ins class="diff-chg">with
</ins>
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 17</span>: Specifying the type for a node</div><pre class="example">{
...
  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
  &quot;<span class="diff">@type</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/Person</span>&quot;,
...
}
</pre>
</div>
<p>
A
node
can
be
assigned
more
than
one
type
by
using
the
following
markup
pattern:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 18</span>: Specifying multiple types for a node</div><pre class="example">{
...
  &quot;@id&quot;: &quot;http://example.org/places#BrewEats&quot;,
  &quot;<span class="diff">@type</span>&quot;: <span class="diff">[&quot;http://schema.org/Restaurant&quot;, &quot;http://schema.org/Brewery&quot;]</span>
...
}
</pre>
</div>
<p>
<ins class="diff-new">The
value
of
a
</ins><code><ins class="diff-new">
@type
</ins></code><ins class="diff-new">
key
may
also
be
a
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><ins class="diff-new">
defined
in
the
</ins><a class="tref internalDFN" title="active_context" href="#dfn-active_context"><ins class="diff-new">
active
context
</ins></a>:</p><div class="example"><div class="example-title"><span>Example 19</span>: Using a term to specify the type</div><pre class="example">{<ins class="diff-new">
  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,
  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
</ins>  <span class="diff">&quot;@type&quot;: &quot;Person&quot;</span>,<ins class="diff-new">
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</ins></pre></div>
</section>
<section id="string-internationalization">
<h3>
<span class="secno">
<del class="diff-old">3.10
</del>
<ins class="diff-chg">5.6
</ins>
</span>
String
Internationalization
</h3>
<p>
At
times,
it
is
important
to
annotate
a
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>
with
its
language.
In
JSON-LD
this
is
possible
in
a
variety
of
ways.
Firstly,
it
is
possible
to
define
a
default
language
for
a
JSON-LD
document
by
setting
the
<code>
@language
</code>
key
in
the
<code>
@context
</code>
or
in
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
definition:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 20</span>: Setting the default language of a JSON-LD document</div><pre class="example">{
  <span class="diff">&quot;@context&quot;:
  {
    ...
    &quot;@language&quot;: &quot;ja&quot;
  },</span>
  &quot;name&quot;: <span class="diff">&quot;花澄&quot;</span>,
  &quot;occupation&quot;: <span class="diff">&quot;科学者&quot;</span>
}
</pre>
</div>
<p>
The
example
above
would
associate
the
<code>
ja
</code>
language
code
with
the
two
<a class="tref internalDFN" title="string" href="#dfn-string">
<del class="diff-old">string
</del>
<ins class="diff-chg">strings
</ins>
</a>
<del class="diff-old">s
</del>
<em>
花澄
</em>
and
<em>
科学者
</em>.
Languages
<del class="diff-old">must
be
well-formed
language
tags
according
to
</del>
<ins class="diff-chg">codes
are
defined
in
</ins>
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
].
</p>
<p>
It
is
possible
to
override
the
default
language
by
using
<del class="diff-old">the
</del>
<ins class="diff-chg">an
</ins><a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value">
expanded
<del class="diff-old">form
of
a
value:
</del>
<ins class="diff-chg">value
</ins></a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 21</span>: Overriding default language using an expanded value</div><pre class="example">{
  &quot;@context&quot;: {
    ...
    &quot;@language&quot;: &quot;ja&quot;
  },
  &quot;name&quot;: &quot;花澄&quot;,
  &quot;occupation&quot;: <span class="diff">{
    &quot;@value&quot;: &quot;Scientist&quot;,
    &quot;@language&quot;: &quot;en&quot;
  }</span>
}
</pre>
</div>
<p>
It
is
also
possible
to
override
the
default
language
or
specify
a
plain
value
by
omitting
the
<code>
@language
</code>
tag
or
setting
it
to
<code>
null
</code>
when
expressing
the
<a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value">
expanded
<del class="diff-old">value:
</del>
<ins class="diff-chg">value
</ins></a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 22</span>: Removing language information using an expanded value</div><pre class="example">{
  &quot;@context&quot;: {
    ...
    &quot;@language&quot;: &quot;ja&quot;
  },
  &quot;name&quot;: <span class="diff">{
    &quot;@value&quot;: &quot;Frank&quot;
  },</span>
  &quot;occupation&quot;: <span class="diff"> {
    &quot;@value&quot;: &quot;Ninja&quot;,
    &quot;@language&quot;: &quot;en&quot;
  }</span>,
  &quot;speciality&quot;: &quot;手裏剣&quot;
}
</pre>
</div>
<del class="diff-old">Note
</del>
<p>
Please
note
that
language
associations
<del class="diff-old">must
</del>
<ins class="diff-chg">can
</ins>
only
be
applied
to
plain
literal
<a class="tref internalDFN" title="string" href="#dfn-string">
<del class="diff-old">string
s.
</del>
<ins class="diff-chg">strings
</ins></a>.
That
is,
<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
typed
<del class="diff-old">value
</del>
<ins class="diff-chg">values
</ins>
</a>
<del class="diff-old">s
</del>
or
values
that
are
subject
to
<a href="#type-coercion" class="sec-ref">
<span class="secno">
<del class="diff-old">4.6
</del>
<ins class="diff-chg">6.6
</ins>
</span>
<span class="sec-title">
Type
Coercion
</span>
</a>
<del class="diff-old">won't
</del>
<ins class="diff-chg">cannot
</ins>
be
language
tagged.
</p>
<p>
To
clear
the
default
language
for
a
subtree,
<code>
@language
</code>
can
be
set
to
<code>
null
</code>
in
a
<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
local
context
</a>
as
follows:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 23</span>: Clearing default language</div><pre class="example">{
  &quot;@context&quot;: {
    ...
    &quot;@language&quot;: &quot;ja&quot;
  },
  &quot;name&quot;: &quot;花澄&quot;,
  &quot;details&quot;: {
<span class="diff">    &quot;@context&quot;: {
      &quot;@language&quot;: null
    },</span>
    &quot;occupation&quot;: &quot;Ninja&quot;
  }
}
</pre>
</div>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
JSON-LD
allows
one
to
associate
language
information
with
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
s.
</del>
<ins class="diff-chg">terms
</ins></a>.
See
<a href="#expanded-term-definition" class="sec-ref">
<span class="secno">
<del class="diff-old">4.5
</del>
<ins class="diff-chg">6.5
</ins>
</span>
<span class="sec-title">
Expanded
Term
Definition
</span>
</a>
for
more
details.
</p>
</div>
</section>
<section id="json-ld-syntax">
<h3>
<span class="secno">
<del class="diff-old">3.11
</del>
<ins class="diff-chg">5.7
</ins>
</span>
JSON-LD
Syntax
</h3>
<p>
A
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
document
</a>
is
first,
and
foremost,
a
JSON
document
(as
defined
in
[
<cite>
<a class="bibref" href="#bib-RFC4627">
RFC4627
</a>
</cite>
<del class="diff-old">]),
and
any
syntactically
correct
JSON
document
must
be
processed
by
a
conforming
JSON-LD
processor.
</del>
<ins class="diff-chg">]).
</ins>
However,
JSON-LD
describes
a
specific
syntax
to
use
for
expressing
Linked
Data.
This
includes
the
use
of
specific
keywords,
as
identified
in
<a href="#syntax-tokens-and-keywords" class="sec-ref">
<span class="secno">
<del class="diff-old">3.4
</del>
<ins class="diff-chg">3.2
</ins>
</span>
<span class="sec-title">
Syntax
Tokens
and
Keywords
</span>
</a>
for
expressing
<a title="node object">
node
<del class="diff-old">definitions
</del>
<ins class="diff-chg">objects
</ins>
</a>,
values,
and
the
<a href="#dfn-context" class="internalDFN">
context
</a>.
See
<a href="#json-ld-grammar" class="sec-ref">
<span class="secno">
<del class="diff-old">A.
</del>
<ins class="diff-chg">B.
</ins>
</span>
<span class="sec-title">
JSON-LD
Grammar
</span>
</a>
for
authoring
<del class="diff-old">guidelines
and
a
BNF
description
of
JSON-LD.
</del>
<ins class="diff-chg">guidelines.
</ins>
</p>
</section>
</section>
<section id="advanced-concepts">
<h2>
<span class="secno">
<del class="diff-old">4.
</del>
<ins class="diff-chg">6.
</ins>
</span>
Advanced
Concepts
</h2>
<em>
This
section
is
normative.
</em>
<p>
JSON-LD
has
a
number
of
features
that
provide
functionality
above
and
beyond
the
core
functionality
described
above.
The
following
section
describes
this
advanced
functionality
in
more
detail.
</p>
<section id="compact-iris">
<h3>
<span class="secno">
<del class="diff-old">4.1
</del>
<ins class="diff-chg">6.1
</ins>
</span>
Compact
IRIs
</h3>
<p>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">Term
</del>
<ins class="diff-chg">Terms
</ins>
</a>
<del class="diff-old">s
</del>
in
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
Linked
Data
</a>
documents
may
draw
from
a
number
of
different
<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
vocabularies
</a>.
At
times,
declaring
every
single
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
that
a
document
uses
can
require
the
developer
to
declare
tens,
if
not
hundreds
of
potential
<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
vocabulary
</a>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
that
are
used
across
an
application.
This
is
a
concern
for
at
least
two
reasons:
the
first
is
the
cognitive
load
on
the
developer
of
remembering
all
of
the
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
s,
</del>
<ins class="diff-chg">terms
</ins></a>,
and
the
second
is
the
serialized
size
of
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
if
it
is
specified
inline.
In
order
to
address
these
issues,
the
concept
of
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
is
introduced.
</p>
<p>
A
<dfn title="compact_iri" id="dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</dfn>
is
a
way
of
expressing
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
using
a
<em>
prefix
</em>
and
<em>
suffix
</em>
separated
by
a
colon
(
<code>:
</code>
)
which
is
similar
to
the
<cite>
<a href="http://www.w3.org/TR/rdfa-core/#s_curies">
CURIE
Syntax
</a>
</cite>
in
[
<cite>
<a class="bibref" href="#bib-RDFA-CORE">
RDFA-CORE
</a>
</cite>
].
The
<dfn title="prefix" id="dfn-prefix">
prefix
</dfn>
is
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
taken
from
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>
and
is
a
short
string
identifying
a
particular
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
in
a
JSON-LD
document.
For
example,
the
prefix
<code>
foaf
</code>
may
be
used
as
a
short
hand
for
the
Friend-of-a-Friend
vocabulary,
which
is
identified
using
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<code>
http://xmlns.com/foaf/0.1/
</code>.
A
developer
may
append
any
of
the
FOAF
<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
vocabulary
</a>
terms
to
the
end
of
the
prefix
to
specify
a
short-hand
version
of
the
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
for
the
<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
vocabulary
</a>
term.
For
example,
<code>
foaf:name
</code>
would
be
expanded
out
to
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<code>
http://xmlns.com/foaf/0.1/name
</code>.
Instead
of
having
to
remember
and
type
out
the
entire
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>,
the
developer
can
instead
use
the
prefix
in
their
JSON-LD
markup.
</p>
<p>
Terms
are
interpreted
as
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">s
</del>
if
they
contain
at
least
one
colon
and
the
first
colon
is
not
followed
by
two
slashes
(
<code>
//
</code>,
as
in
<code>
http://example.com
</code>
).
To
generate
the
full
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
the
value
is
first
split
into
a
<em>
prefix
</em>
and
<em>
suffix
</em>
at
the
first
occurrence
of
a
colon
(
<code>:
</code>
).
If
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>
contains
a
term
mapping
for
<em>
prefix
</em>,
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
is
generated
by
prepending
the
mapped
<em>
prefix
</em>
to
the
(possibly
empty)
<em>
suffix
</em>
using
textual
concatenation.
If
no
prefix
mapping
is
defined,
the
value
is
interpreted
as
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
If
the
prefix
is
an
underscore
(
<code>
_
</code>
),
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
remains
unchanged.
<del class="diff-old">This
effectively
means
that
every
term
containing
a
colon
will
be
interpreted
by
a
JSON-LD
processor
as
an
IRI
.
</del>
</p>
<p>
Consider
the
following
example:
</p>
<del class="diff-old">  {
</del>
  <div class="example"><div class="example-title"><span>Example 24</span>: Compact IRIs</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;dc&quot;: &quot;http://purl.org/dc/elements/1.1/&quot;,</span>
    <span class="diff">&quot;ex&quot;: &quot;http://example.org/vocab#&quot;</span>
  },
  &quot;@id&quot;: &quot;http://example.org/library&quot;,
  &quot;@type&quot;: <span class="diff">&quot;ex:Library&quot;</span>,
  <span class="diff">&quot;ex:contains&quot;</span>:
  {
    &quot;@id&quot;: &quot;http://example.org/library/the-republic&quot;,
    &quot;@type&quot;: <span class="diff">&quot;ex:Book&quot;</span>,
    <span class="diff">&quot;dc:creator&quot;</span>: &quot;Plato&quot;,
    <span class="diff">&quot;dc:title&quot;</span>: &quot;The Republic&quot;,
    <span class="diff">&quot;ex:contains&quot;</span>:
    {
      &quot;@id&quot;: &quot;http://example.org/library/the-republic#introduction&quot;,
      &quot;@type&quot;: <span class="diff">&quot;ex:Chapter&quot;</span>,
      <span class="diff">&quot;dc:description&quot;</span>: &quot;An introductory chapter on The Republic.&quot;,
      <span class="diff">&quot;dc:title&quot;</span>: &quot;The Introduction&quot;
    }
  }
}
</pre>
</div>
<p>
In
this
example,
two
different
<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
vocabularies
</a>
are
referred
to
using
prefixes.
Those
prefixes
are
then
used
as
type
and
property
values
using
the
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<code>
prefix:suffix
</code>
notation.
</p>
<p>
It's
also
possible
to
use
compact
IRIs
within
the
context
as
shown
in
the
following
example:
</p>
<del class="diff-old">  {
</del>
  <div class="example"><div class="example-title"><span>Example 25</span>: Using vocabularies</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
    <span class="diff">&quot;foaf:homepage&quot;</span>: { &quot;@type&quot;: &quot;@id&quot; },
    &quot;picture&quot;: { &quot;@id&quot;: <span class="diff">&quot;foaf:depiction&quot;</span>, &quot;@type&quot;: &quot;@id&quot; }
  },
  &quot;@id&quot;: &quot;http://me.markus-lanthaler.com/&quot;,
  &quot;@type&quot;: &quot;foaf:Person&quot;,
  &quot;foaf:name&quot;: &quot;Markus Lanthaler&quot;,
  &quot;foaf:homepage&quot;: &quot;http://www.markus-lanthaler.com/&quot;,
  &quot;picture&quot;: &quot;http://twitter.com/account/profile_image/markuslanthaler&quot;
}
</pre>
</div>
</section>
<section id="typed-values">
<h3>
<span class="secno">
<del class="diff-old">4.2
</del>
<ins class="diff-chg">6.2
</ins>
</span>
Typed
Values
</h3>
<p>
A
value
with
an
associated
type,
also
known
as
a
<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
typed
value
<del class="diff-old">,
</del>
</a>,
is
indicated
by
associating
a
value
with
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
which
indicates
the
value's
type.
Typed
values
may
be
expressed
in
JSON-LD
in
three
ways:
</p>
<ol>
<li>
By
utilizing
the
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
when
defining
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
within
a
<code>
@context
</code>
section.
</li>
<li>
By
utilizing
<del class="diff-old">the
</del>
<ins class="diff-chg">an
</ins><a class="tref internalDFN" title="expanded_typed_value" href="#dfn-expanded_typed_value">
expanded
<del class="diff-old">form
for
specifying
values.
</del>
<ins class="diff-chg">typed
value
</ins></a>.
</li>
<li>
By
using
a
native
JSON
type
such
as
<a class="tref internalDFN" title="number" href="#dfn-number">
number
</a>,
<a class="tref internalDFN" title="true" href="#dfn-true">
true
</a>,
or
<a class="tref internalDFN" title="false" href="#dfn-false">
false
</a>.
</li>
</ol>
<p>
The
first
example
uses
the
<code>
@type
</code>
keyword
to
associate
a
type
with
a
particular
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
in
the
<code>
@context
</code>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 26</span>: Expanded term definition with type coercion</div><pre class="example">{
  <span class="diff">&quot;@context&quot;:
  {
    &quot;modified&quot;:
    {
      &quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;,
      &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;
    }
  },</span>
...
  &quot;modified&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
...
}
</pre>
</div>
<p>
The
<em>
modified
</em>
key's
value
above
is
automatically
type
coerced
to
a
datetime
value
because
of
the
information
specified
in
the
<code>
@context
</code>.
</p>
<p>
The
second
example
uses
the
expanded
form
of
setting
the
type
information
in
the
body
of
a
JSON-LD
document:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 27</span>: Expanded value with type</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;modified&quot;:
    {
      &quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;
    }
  },
...
  &quot;modified&quot;:
  <span class="diff">{
    &quot;@value&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
    &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;
  }</span>
...
}
</pre>
</div>
<p>
Both
examples
above
would
generate
the
value
<code>
2010-05-29T14:17:39+02:00
</code>
with
the
type
<code>
http://www.w3.org/2001/XMLSchema#dateTime
</code>.
Note
that
it
is
also
possible
to
use
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
or
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
to
express
the
value
of
a
type.
</p>
<p>
The
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
is
also
used
to
associate
a
type
with
a
<a class="tref internalDFN" title="node" href="#dfn-node">
node
</a>.
The
concept
of
<del class="diff-old">an
</del>
<ins class="diff-chg">a
</ins>
<dfn title="node_type" id="dfn-node_type">
node
type
</dfn>
and
a
<dfn title="value_type" id="dfn-value_type">
value
type
</dfn>
are
different.
This
is
similar
to
object-oriented
programming
languages
where
both
scalar
and
structured
types
use
the
same
class
inheritance
mechanism,
even
though
scalar
types
and
structured
types
are
inherently
different.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 28</span>: Example demonstrating the context-sensitivity for @type</div><pre class="example">{
...
  &quot;@id&quot;: &quot;http://example.org/posts#TripToWestVirginia&quot;,
  <span class="diff">&quot;@type&quot;: &quot;http://schema.org/BlogPosting&quot;</span>,
  &quot;modified&quot;:
  {
    &quot;@value&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
    <span class="diff">&quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;</span>
  }
...
}
</pre>
</div>
<p>
The
first
use
of
<code>
@type
</code>
associates
a
<a class="tref internalDFN" title="node_type" href="#dfn-node_type">
node
type
</a>
(
<code>
http://schema.org/BlogPosting
</code>
)
with
the
<a class="tref internalDFN" title="node" href="#dfn-node">
node
</a>,
which
is
expressed
using
the
<code>
@id
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>.
The
second
use
of
<code>
@type
</code>
associates
a
<a class="tref internalDFN" title="value_type" href="#dfn-value_type">
value
type
</a>
(
<code>
http://www.w3.org/2001/XMLSchema#dateTime
</code>
)
with
the
value
expressed
using
the
<code>
@value
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>.
As
a
general
rule,
when
<code>
@value
</code>
and
<code>
@type
</code>
are
used
in
the
same
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>,
the
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
is
expressing
a
<a class="tref internalDFN" title="value_type" href="#dfn-value_type">
value
type
</a>.
Otherwise,
the
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
is
expressing
a
<a class="tref internalDFN" title="node_type" href="#dfn-node_type">
node
type
</a>.
</p>
</section>
<section id="language-tagged-strings">
<h3>
<span class="secno">
<del class="diff-old">4.3
</del>
<ins class="diff-chg">6.3
</ins>
</span>
Language-tagged
Strings
</h3>
<p>
A
string
with
an
associated
language,
also
known
as
a
<a class="tref internalDFN" title="language-tagged_string" href="#dfn-language-tagged_string">
language-tagged
string
<del class="diff-old">,
</del>
</a>,
is
indicated
by
associating
a
string
with
<del class="diff-old">an
</del>
<ins class="diff-chg">a
</ins>
language
code
as
defined
in
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
].
Language-tagged
strings
may
be
expressed
in
JSON-LD
in
four
ways:
</p>
<ol>
<li>
By
defining
a
global
language
using
the
<code>
@language
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
within
a
<code>
@context
</code>
section.
</li>
<li>
By
utilizing
the
<code>
@language
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
when
defining
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
within
a
<code>
@context
</code>
section.
</li>
<li>
By
utilizing
<del class="diff-old">the
</del>
<ins class="diff-chg">an
</ins><a class="tref internalDFN" title="expanded_language-tagged_string" href="#dfn-expanded_language-tagged_string">
expanded
<del class="diff-old">form
for
specifying
values.
</del>
<ins class="diff-chg">language-tagged
string
</ins></a>.
</li>
<li>
By
utilizing
<ins class="diff-new">a
</ins><a class="tref internalDFN" title="language_map" href="#dfn-language_map"><ins class="diff-new">
language
map
</ins></a>,<ins class="diff-new">
provided
</ins>
the
<ins class="diff-new">underlying
</ins><code><ins class="diff-new">
term
</ins></code><ins class="diff-new">
is
defined
with
a
</ins>
<code>
@container
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
<del class="diff-old">with
a
</del>
<ins class="diff-chg">whose
</ins>
value
<del class="diff-old">of
</del>
<ins class="diff-chg">is
</ins>
<code>
@language
</code>
<del class="diff-old">when
defining
a
term
</del>
within
a
<code>
@context
</code>
section.
<del class="diff-old">This
usage
pattern
is
called
a
language
map
.
</del>
</li>
</ol>
<p>
The
first
example
uses
the
<code>
@language
</code>
keyword
to
associate
a
type
with
a
particular
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
in
the
<code>
@context
</code>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 29</span>: Expanded term definition with language coercion</div><pre class="example">{
  <span class="diff">&quot;@context&quot;:
  {
    &quot;title&quot;:
    {
      &quot;@id&quot;: &quot;http://purl.org/dc/terms/title&quot;,
      &quot;@language&quot;: &quot;en&quot;
    }
  },</span>
...
  &quot;title&quot;: &quot;JSON-LD Syntax&quot;,
...
}
</pre>
</div>
<p>
The
<em>
modified
</em>
key's
value
above
is
automatically
language
coerced
to
a
English
value
because
of
the
information
specified
in
the
<code>
@context
</code>.
</p>
<p>
The
second
example
uses
the
expanded
form
of
setting
the
language
information
in
the
body
of
a
JSON-LD
document:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 30</span>: Expanded value with language</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;title&quot;:
    {
      &quot;@id&quot;: &quot;http://purl.org/dc/terms/title&quot;
    }
  },
...
  &quot;title&quot;:
  <span class="diff">{
    &quot;@value&quot;: &quot;JSON-LD Syntax&quot;,
    &quot;@language&quot;: &quot;en&quot;
  }</span>
...
}
</pre>
</div>
<p>
Both
examples
above
would
generate
the
value
<code>
JSON-LD
Syntax
</code>
tagged
with
the
language
<code>
en
</code>
;
which
is
the
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
]
code
for
the
English
language.
</p>
<p>
Systems
that
support
multiple
languages
often
need
to
express
data
values
in
each
language.
Typically,
such
systems
also
try
to
ensure
that
developers
have
a
programatically
easy
way
to
navigate
the
datastructures
for
the
language-specific
data.
In
this
case,
<a class="tref internalDFN" title="language_map" href="#dfn-language_map">
language
<del class="diff-old">map
</del>
<ins class="diff-chg">maps
</ins>
</a>
<del class="diff-old">s
</del>
may
be
utilized.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 31</span>: Language map expressing a property in three languages</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;title&quot;:
    {
<del class="diff-old">      &quot;@id&quot;: &quot;http://purl.org/dc/terms/title&quot;
      &quot;@container&quot;: &quot;@language&quot;
</del>
<ins class="diff-chg">      &quot;@id&quot;: &quot;http://purl.org/dc/terms/title&quot;,
</ins>      <span class="diff">&quot;@container&quot;: &quot;@language&quot;</span>
    }
  },
...
  &quot;title&quot;:
  <span class="diff">{
    &quot;en&quot;: &quot;JSON-LD Syntax&quot;,
    &quot;ru&quot;: &quot;JSON-LD Синтаксис&quot;,
    &quot;ja&quot;: &quot;JSON-LDの構文&quot;
  }</span>
...
}
</pre>
</div>
<p>
In
the
example
above,
the
title
is
expressed
in
three
languages;
English,
Russian,
and
Japanese.
To
access
the
data
above
in
a
programming
language
supporting
dot-notation
accessors
for
object
properties,
a
developer
may
use
the
<code>
property.language
</code>
pattern.
For
example,
to
access
the
Japanese
version
of
the
title,
a
developer
would
use
the
following
code
snippet:
<code>
obj.title.ja
</code>.
</p>
</section>
<section id="referencing-contexts-from-json-documents">
<h3>
<span class="secno">
<del class="diff-old">4.4
</del>
<ins class="diff-chg">6.4
</ins>
</span>
Referencing
Contexts
from
JSON
Documents
</h3>
<p>
Ordinary
JSON
documents
can
be
transformed
into
JSON-LD
documents
by
referencing
to
an
external
JSON-LD
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
in
an
HTTP
Link
Header.
Doing
this
allows
JSON
to
be
unambiguously
machine-readable
without
requiring
developers
to
drastically
change
their
workflow
and
provides
an
upgrade
path
for
existing
infrastructure
without
breaking
existing
clients
that
rely
on
the
<code>
application/json
</code>
media
type.
</p>
<p>
In
order
to
use
an
external
context
with
an
ordinary
JSON
document,
an
author
<em class="rfc2119" title="must">
must
</em>
specify
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
to
a
valid
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
document
</a>
in
an
HTTP
Link
Header
[
<cite>
<a class="bibref" href="#bib-RFC5988">
RFC5988
</a>
</cite>
]
using
the
<code>
<del class="diff-old">describedby
</del>
<ins class="diff-chg">http://www.w3.org/ns/json-ld#context
</ins>
</code>
link
relation.
The
referenced
document
<em class="rfc2119" title="must">
must
</em>
have
a
top-level
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>.
The
<code>
@context
</code>
subtree
within
that
object
is
added
to
the
top-level
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
of
the
referencing
document.
If
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
is
at
the
top-level
of
the
referencing
document
and
its
items
are
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definitions
</del>
<ins class="diff-chg">objects
</ins>
</a>,
the
<code>
@context
</code>
subtree
is
added
to
all
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
items.
All
extra
information
located
outside
of
the
<code>
@context
</code>
subtree
in
the
referenced
document
<em class="rfc2119" title="must">
must
</em>
be
discarded.
</p>
<p>
The
following
example
demonstrates
the
use
of
an
external
context
with
an
ordinary
JSON
document:
</p>
<del class="diff-old">GET /ordinary-json-document.json HTTP/1.1
</del>
<div class="example"><div class="example-title"><span>Example 32</span>: Specifing context through HTTP header</div><pre class="example">GET /ordinary-json-document.json HTTP/1.1
Host: example.com
Accept: application/ld+json,application/json,*/*;q=0.1
====================================
HTTP/1.0 200 OK
...
Content-Type: <span class="diff">application/json</span>
<span class="diff">Link: &lt;http://json-ld.org/contexts/person.jsonld&gt;; rel=&quot;http://www.w3.org/ns/json-ld#context&quot;; type=&quot;application/ld+json&quot;</span>
{
  &quot;name&quot;: &quot;Markus Lanthaler&quot;,
  &quot;homepage&quot;: &quot;http://www.markus-lanthaler.com/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/markuslanthaler&quot;
}
</pre>
</div>
<del class="diff-old">Note
</del>
<p>
<ins class="diff-chg">Please
note
that
</ins><a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
documents
</a>
served
with
the
<code>
application/ld+json
</code>
media
type
<em class="rfc2119" title="must">
must
</em>
have
all
context
information,
including
references
to
external
contexts,
within
the
body
of
the
document.
<ins class="diff-new">Contexts
linked
via
a
</ins><code><ins class="diff-new">
http://www.w3.org/ns/json-ld#context
</ins></code><ins class="diff-new">
HTTP
Link
Header
</ins><em class="rfc2119" title="must"><ins class="diff-new">
must
</ins></em><ins class="diff-new">
be
ignored
for
such
documents.
</ins>
</p>
</section>
<section id="expanded-term-definition">
<h3>
<span class="secno">
<del class="diff-old">4.5
</del>
<ins class="diff-chg">6.5
</ins>
</span>
Expanded
Term
Definition
</h3>
<p>
Within
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
definition,
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
may
be
defined
using
an
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
<del class="diff-old">notation
</del>
<ins class="diff-chg">term
definition
</ins></a>
to
allow
for
additional
information
associated
with
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
to
be
specified
(see
also
<a href="#type-coercion" class="sec-ref">
<span class="secno">
<del class="diff-old">4.6
</del>
<ins class="diff-chg">6.6
</ins>
</span>
<span class="sec-title">
Type
Coercion
</span>
</a>
and
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
</a>
).
</p>
<p>
Instead
of
using
a
string
representation
of
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>,
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
may
be
specified
using
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
having
an
<code>
@id
</code>
<del class="diff-old">key.
The
value
of
the
@id
key
must
be
either
</del>
<ins class="diff-chg">key,
and
</ins>
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>,
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
or
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">.
Such
an
object
is
called
a
node
reference
.
</del>
</a>
<ins class="diff-chg">as
value.
</ins>
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 33</span>: Expanded term definition</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;foaf&quot;: <span class="diff">{ &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/&quot; }</span>,
    &quot;name&quot;: <span class="diff">{ &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot; }</span>,
    &quot;homepage&quot;: <span class="diff">{ &quot;@id&quot;: &quot;foaf:homepage&quot; }</span>,
    &quot;depiction&quot;: <span class="diff">{ &quot;@id&quot;: &quot;foaf:depiction&quot; }</span>
  },
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</pre>
</div>
<p>
This
allows
additional
information
to
be
associated
with
the
term.
This
may
be
used
for
<a href="#type-coercion" class="sec-ref">
<span class="secno">
<del class="diff-old">4.6
</del>
<ins class="diff-chg">6.6
</ins>
</span>
<span class="sec-title">
Type
Coercion
</span>
</a>,
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
<del class="diff-old">),
</del>
</a>,
or
to
associate
language
information
with
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
as
shown
in
the
following
example:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 34</span>: Expanded term definition with language</div><pre class="example">{
  &quot;@context&quot;: {
    ...
    &quot;ex&quot;: &quot;http://example.com/&quot;,
    &quot;@language&quot;: &quot;ja&quot;,
    &quot;name&quot;: { &quot;@id&quot;: &quot;ex:name&quot;, <span class="diff">&quot;@language&quot;: null</span> },
    &quot;occupation&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot; },
    &quot;occupation_en&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot;, <span class="diff">&quot;@language&quot;: &quot;en&quot;</span> },
    &quot;occupation_cs&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot;, <span class="diff">&quot;@language&quot;: &quot;cs&quot;</span> }
  },
  <span class="diff">&quot;name&quot;: &quot;Yagyū Muneyoshi&quot;,
  &quot;occupation&quot;: &quot;忍者&quot;,
  &quot;occupation_en&quot;: &quot;Ninja&quot;,
  &quot;occupation_cs&quot;: &quot;Nindža&quot;,</span>
  ...
}
</pre>
</div>
<p>
The
example
above
would
associate
<em>
忍者
</em>
with
the
specified
default
language
code
<code>
ja
</code>,
<em>
Ninja
</em>
with
the
language
code
<code>
en
</code>,
and
<em>
Nindža
</em>
with
the
language
code
<code>
cs
</code>.
The
value
of
<code>
name
</code>,
<em>
Yagyū
Muneyoshi
</em>
wouldn't
be
associated
with
any
language
code
since
<code>
@language
</code>
was
reset
to
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>
in
the
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
<del class="diff-old">definition.
</del>
<ins class="diff-chg">definition
</ins></a>.
</p>
<p>
Expanded
terms
may
also
be
defined
using
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
IRIs
</a>
or
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
IRIs
</a>
as
keys.
If
the
definition
does
not
include
an
<code>
@id
</code>
key,
the
expanded
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
is
determined
by
performing
expansion
of
the
key
within
the
current
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
<del class="diff-old">context.
</del>
<ins class="diff-chg">context
</ins></a>.
This
mechanism
is
mainly
used
to
associate
type
or
language
information
with
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
or
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
While
it
is
possible
to
define
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
or
an
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
to
expand
to
some
other
unrelated
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
(for
example,
<code>
foaf:name
</code>
expanding
to
<code>
http://example.org/unrelated#species
</code>
),
such
usage
is
strongly
discouraged.
</p>
</div>
</section>
<section id="type-coercion">
<h3>
<span class="secno">
<del class="diff-old">4.6
</del>
<ins class="diff-chg">6.6
</ins>
</span>
Type
Coercion
</h3>
<p>
JSON-LD
supports
the
coercion
of
values
to
particular
data
types.
Type
<dfn title="coercion" id="dfn-coercion">
coercion
</dfn>
allows
someone
deploying
JSON-LD
to
coerce
the
incoming
or
outgoing
values
to
the
proper
data
type
based
on
a
mapping
of
data
type
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">s
</del>
to
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
s.
</del>
<ins class="diff-chg">terms
</ins></a>.
Using
type
coercion,
value
representation
is
preserved
without
requiring
the
data
type
to
be
specified
with
each
piece
of
data.
</p>
<p>
Type
coercion
is
specified
within
an
<a href="#expanded-term-definition" class="sec-ref">
<span class="secno">
<del class="diff-old">4.5
</del>
<ins class="diff-chg">6.5
</ins>
</span>
<span class="sec-title">
Expanded
Term
Definition
</span>
</a>
using
the
<code>
@type
</code>
key.
The
value
of
this
key
<del class="diff-old">represents
a
type
IRI
and
must
take
the
form
of
a
term
,
compact
IRI
</del>
<ins class="diff-chg">expands
to
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">,
absolute
</del>
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">,
or
</del>
</a>.
<ins class="diff-chg">Alternatively,
</ins>
the
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
<code>
@id
<del class="diff-old">.
Specifying
@id
</del>
</code>
<del class="diff-old">indicates
</del>
<ins class="diff-chg">may
be
used
as
value
to
indicate
</ins>
that
within
the
body
of
a
JSON-LD
document,
a
string
value
of
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
coerced
to
<code>
@id
</code>
is
to
be
interpreted
as
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
</p>
<p>
<a class="tref internalDFN" title="term" href="#dfn-term">
Terms
</a>
or
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
IRIs
</a>
used
as
the
value
of
a
<code>
@type
</code>
key
may
be
defined
within
the
same
context.
This
means
that
one
may
specify
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
like
<code>
xsd
</code>
and
then
use
<code>
xsd:integer
</code>
within
the
same
context
<del class="diff-old">definition
-
the
JSON-LD
processor
will
be
able
to
determine
the
proper
expansion
for
xsd:integer
.
</del>
<ins class="diff-chg">definition.
</ins>
</p>
<p>
The
example
below
demonstrates
how
a
JSON-LD
author
can
coerce
values
to
<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
typed
<del class="diff-old">value
s,
</del>
<ins class="diff-chg">values
</ins></a>,
IRIs
and
lists.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 35</span>: Expanded term definition with types</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;age&quot;:
    <span class="diff">{
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;,
      &quot;@type&quot;: &quot;xsd:integer&quot;
    }</span>,
    &quot;homepage&quot;:
    <span class="diff">{
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;,
      &quot;@container&quot;: &quot;@list&quot;
    }</span>
  },
<ins class="diff-new">  &quot;@id&quot;: &quot;http://example.com/people#john&quot;,
</ins>
  &quot;name&quot;: &quot;John Smith&quot;,
  &quot;age&quot;: <span class="diff">&quot;41&quot;</span>,
  &quot;homepage&quot;:
  <span class="diff">[
    &quot;http://personal.example.org/&quot;,
    &quot;http://work.example.com/jsmith/&quot;
  ]</span>
}
</pre>
</div>
<p>
The
<del class="diff-old">example
</del>
<ins class="diff-chg">markup
shown
</ins>
above
would
generate
the
following
<del class="diff-old">Turtle:
</del>
<ins class="diff-chg">data.
The
data
has
no
inherent
order
except
for
the
values
the
</ins><code><ins class="diff-chg">
http://xmlns.com/foaf/0.1/homepage
</ins></code><ins class="diff-chg">
property
which
represent
an
ordered
list.
</ins>
</p>
<del class="diff-old">@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
</del>
<table class="example">
<thead>
<tr>
<del class="diff-old">[ foaf:name &quot;John Smith&quot;;
  foaf:age  &quot;41&quot;^^xsd:integer;
  foaf:homepage ( &lt;http://personal.example.org/&gt; &lt;http://work.example.com/jsmith/&gt; )
]
.
</del>
<th>
<ins class="diff-chg">Subject
</ins></th><th><ins class="diff-chg">
Property
</ins></th><th><ins class="diff-chg">
Object
</ins></th><th><ins class="diff-chg">
Datatype
</ins></th></tr>
</thead>
<tbody>
<tr>
<td>
<ins class="diff-chg">http://example.com/people#john
</ins></td><td><ins class="diff-chg">
http://xmlns.com/foaf/0.1/name
</ins></td><td><ins class="diff-chg">
John
Smith
</ins></td><td></td></tr><tr><td><ins class="diff-chg">
http://example.com/people#john
</ins></td><td><ins class="diff-chg">
http://xmlns.com/foaf/0.1/age
</ins></td><td><ins class="diff-chg">
41
</ins></td><td><ins class="diff-chg">
http://www.w3.org/2001/XMLSchema#integer
</ins></td></tr><tr><td rowspan="2"><ins class="diff-chg">
http://example.com/people#john
</ins></td><td rowspan="2"><ins class="diff-chg">
http://xmlns.com/foaf/0.1/homepage
</ins></td><td><ins class="diff-chg">
http://personal.example.org/
</ins></td><td></td></tr><tr><td><ins class="diff-chg">
http://work.example.com/jsmith/
</ins></td><td></td></tr></tbody></table>
<p>
Terms
may
also
be
defined
using
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
IRIs
</a>
or
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
IRIs
</a>.
This
allows
coercion
rules
to
be
applied
to
keys
which
are
not
represented
as
a
simple
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>.
For
example:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 36</span>: Term definitions using compact and absolute IRIs</div><pre class="example">{
  &quot;@context&quot;:
  {
<del class="diff-old">    ,
</del>
<ins class="diff-chg">    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
</ins>
    &quot;<span class="diff">foaf:age</span>&quot;:
    {
      <span class="diff">&quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;</span>,
      &quot;@type&quot;: &quot;xsd:integer&quot;
    },
<del class="diff-old">    &quot;&quot;:
    {
</del>
<ins class="diff-chg">    &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;:
    {
</ins>
      &quot;@type&quot;: &quot;@id&quot;
<del class="diff-old">    }
</del>
<ins class="diff-chg">    }
</ins>
  },
  &quot;foaf:name&quot;: &quot;John Smith&quot;,
<del class="diff-old">  &quot;foaf:age&quot;: ,
  &quot;foaf:homepage&quot;:
  [
</del>
<ins class="diff-chg">  &quot;<span class="diff">foaf:age</span>&quot;: &quot;41&quot;,
  &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;:
  [
</ins>
    &quot;http://personal.example.org/&quot;,
    &quot;http://work.example.com/jsmith/&quot;
<del class="diff-old">  ]
</del>
<ins class="diff-chg">  ]
</ins>
}
</pre>
</div>
<p>
In
this
case
the
<code>
@id
</code>
definition
<ins class="diff-new">in
the
term
definition
</ins>
is
optional,
but
if
it
does
exist,
the
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
or
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
is
treated
as
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
(not
a
<code>
prefix:suffix
</code>
construct)
so
that
the
actual
definition
of
a
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
prefix
</a>
becomes
unnecessary.
<ins class="diff-new">Type
coercion
is
performed
using
the
unexpanded
value
of
the
key,
which
has
to
match
exactly
an
entry
in
the
</ins><a class="tref internalDFN" title="active_context" href="#dfn-active_context"><ins class="diff-new">
active
context
</ins></a>.
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
Keys
in
the
context
are
treated
as
<a class="tref internalDFN" title="term" href="#dfn-term">
terms
</a>
for
the
purpose
of
expansion
and
value
coercion.
At
times,
this
may
result
in
multiple
representations
for
the
same
expanded
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>.
For
example,
one
could
specify
that
<code>
dog
</code>
and
<code>
cat
</code>
both
expanded
to
<code>
http://example.com/vocab#animal
</code>.
Doing
this
could
be
useful
for
establishing
different
type
coercion
or
language
specification
rules.
It
also
allows
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
(or
even
an
absolute
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
)
to
be
defined
as
something
else
entirely.
For
example,
one
could
specify
that
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
<code>
http://example.org/zoo
</code>
should
expand
to
<code>
http://example.org/river
</code>,
but
this
usage
is
discouraged
because
it
would
lead
to
a
great
deal
of
confusion
among
developers
attempting
to
understand
the
JSON-LD
document.
</p>
</div>
<del class="diff-old">Type
coercion
is
performed
using
the
unexpanded
value
of
the
key,
which
must
have
an
exact
match
for
an
entry
in
the
active
context
.
</del>
</section>
<section id="property-generators">
<h3>
<span class="secno">
<del class="diff-old">4.7
</del>
<ins class="diff-chg">6.7
</ins>
</span>
Property
Generators
</h3>
<p>
At
times,
an
author
may
find
that
they
need
to
express
the
same
value
for
multiple
properties.
The
simplest
approach
to
accomplish
this
goal
would
be
to
do
the
following:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 37</span>: Verbose expression of multiple properties with the same value</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;title1&quot;: &quot;http://purl.org/dc/terms/title&quot;</span>,
    <span class="diff">&quot;title2&quot;: &quot;http://schema.org/name&quot;</span>,
    <span class="diff">&quot;title3&quot;: &quot;http://www.w3.org/2000/01/rdf-schema#label&quot;</span>
  },
  &quot;@id&quot;: &quot;http://example.com/book&quot;,
  <span class="diff">&quot;title1&quot;: &quot;The Count of Monte Cristo&quot;</span>,
  <span class="diff">&quot;title2&quot;: &quot;The Count of Monte Cristo&quot;</span>,
  <span class="diff">&quot;title3&quot;: &quot;The Count of Monte Cristo&quot;</span>
}
</pre>
</div>
<p>
Unfortunately,
the
approach
above
produces
redundant
data
and
would
become
a
publishing
burden
for
large
data
sets.
In
these
situations,
the
author
may
use
a
<dfn title="property_generator" id="dfn-property_generator">
property
generator
</dfn>
to
express
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
<del class="diff-old">once,
but
have
</del>
<ins class="diff-chg">that
maps
to
multiple
</ins><a class="tref internalDFN" title="property" href="#dfn-property"><ins class="diff-chg">
properties
</ins></a><ins class="diff-chg">
in
</ins>
the
<a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph">
JSON-LD
<del class="diff-old">processor
expand
the
single
statement
into
multiple
statements.
</del>
<ins class="diff-chg">graph
</ins></a>.
This
method
can
be
accomplished
by
using
the
following
markup
pattern:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 38</span>: Generating multiple properties using a single term</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;title&quot;: { &quot;@id&quot;: [ &quot;http://purl.org/dc/terms/title&quot;,
                        &quot;http://schema.org/name&quot;,
                        &quot;http://www.w3.org/2000/01/rdf-schema#label&quot; ] }</span>
  },
  &quot;@id&quot;: &quot;http://example.com/book&quot;,
  <span class="diff">&quot;title&quot;: &quot;The Count of Monte Cristo&quot;</span>
}
</pre>
</div>
<p>
While
the
term
above
is
only
used
once
outside
of
the
<code>
@context
</code>,
<del class="diff-old">a
JSON-LD
processor
will
internally
transform
</del>
the
document
above
<del class="diff-old">into
</del>
<ins class="diff-chg">is
equivalent
to
</ins>
the
<del class="diff-old">following
set
of
statements:
</del>
<ins class="diff-chg">following:
</ins>
</p>
<del class="diff-old">&lt;http://example.com/book&gt;
  &lt;http://purl.org/dc/terms/title&gt;
    &quot;The Count of Monte Cristo&quot; .
&lt;http://example.com/book&gt;
  &lt;http://schema.org/name&gt;
    &quot;The Count of Monte Cristo&quot; .
&lt;http://example.com/book&gt;
  &lt;http://www.w3.org/2000/01/rdf-schema#label&gt;
&quot;The
</del>
<table class="example">
<thead>
<tr>
<th>
<ins class="diff-chg">Subject
</ins></th><th><ins class="diff-chg">
Property
</ins></th><th><ins class="diff-chg">
Object
</ins></th></tr></thead><tbody><tr><td><ins class="diff-chg">
http://example.com/book
</ins></td><td><ins class="diff-chg">
http://purl.org/dc/terms/title
</ins></td><td><ins class="diff-chg">
The
</ins>
Count
of
Monte
<del class="diff-old">Cristo&quot;
.
</del>
<ins class="diff-chg">Cristo
</ins></td></tr><tr><td><ins class="diff-chg">
http://example.com/book
</ins></td><td><ins class="diff-chg">
http://schema.org/name
</ins></td><td><ins class="diff-chg">
The
Count
of
Monte
Cristo
</ins></td></tr><tr><td><ins class="diff-chg">
http://example.com/book
</ins></td><td><ins class="diff-chg">
http://www.w3.org/2000/01/rdf-schema#label
</ins></td><td><ins class="diff-chg">
The
Count
of
Monte
Cristo
</ins></td></tr></tbody></table>
</section>
<section id="iri-expansion-within-a-context">
<h3>
<span class="secno">
<del class="diff-old">4.8
</del>
<ins class="diff-chg">6.8
</ins>
</span>
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
Expansion
Within
a
Context
</h3>
<p>
In
general,
normal
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
expansion
rules
apply
anywhere
an
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
is
expected
(see
<a href="#iris" class="sec-ref">
<span class="secno">
<del class="diff-old">3.7
</del>
<ins class="diff-chg">5.3
</ins>
</span>
<span class="sec-title">
IRIs
</span>
</a>
).
Within
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
definition,
this
can
mean
that
terms
defined
within
the
context
may
also
be
used
within
that
context
as
long
as
there
are
no
circular
dependencies.
For
example,
it
is
common
to
use
the
<code>
xsd
</code>
namespace
when
defining
<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
typed
value
</a>
s:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 39</span>: IRI expansion within a context</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;</span>,
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;age&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;,
      &quot;@type&quot;: <span class="diff">&quot;xsd:integer&quot;</span>
    },
    &quot;homepage&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    }
  },
  ...
}
</pre>
</div>
<p>
In
this
example,
the
<code>
xsd
</code>
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
is
defined
and
used
as
a
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
prefix
</a>
for
the
<code>
@type
</code>
coercion
of
the
<code>
age
</code>
property.
</p>
<p>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">Term
</del>
<ins class="diff-chg">Terms
</ins>
</a>
<del class="diff-old">s
</del>
may
also
be
used
when
defining
the
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
of
another
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 40</span>: Using a term to define the IRI of another term within a context</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
    &quot;name&quot;: <span class="diff">&quot;foaf:name&quot;</span>,
    &quot;age&quot;:
    {
      &quot;@id&quot;: <span class="diff">&quot;foaf:age&quot;</span>,
      &quot;@type&quot;: &quot;xsd:integer&quot;
    },
    &quot;homepage&quot;:
    {
      &quot;@id&quot;: <span class="diff">&quot;foaf:homepage&quot;</span>,
      &quot;@type&quot;: &quot;@id&quot;
    }
  },
  ...
}
</pre>
</div>
<p>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
Compact
IRIs
</a>
and
<a class="tref internalDFN" title="iri" href="#dfn-iri">
IRIs
</a>
may
be
used
on
the
left-hand
side
of
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
definition.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 41</span>: Using a compact IRI as a term</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
    &quot;name&quot;: &quot;foaf:name&quot;,
    &quot;<span class="diff">foaf:age</span>&quot;:
    {
      &quot;@type&quot;: &quot;xsd:integer&quot;
    },
    &quot;<span class="diff">foaf:homepage</span>&quot;:
    <span class="diff">{
      &quot;@type&quot;: &quot;@id&quot;
    }</span>
  },
  ...
}
</pre>
</div>
<p>
In
this
example,
the
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
form
is
used
in
two
different
ways.
In
the
first
approach,
<code>
foaf:age
</code>
declares
both
the
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
for
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
(using
short-form)
as
well
as
the
<code>
@type
</code>
associated
with
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>.
In
the
second
approach,
only
the
<code>
@type
</code>
associated
with
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
is
specified.
The
<del class="diff-old">JSON-LD
processor
will
derive
the
</del>
full
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
for
<code>
foaf:homepage
</code>
<ins class="diff-new">is
determined
</ins>
by
looking
up
the
<code>
foaf
</code>
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
prefix
</a>
in
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>.
</p>
<p>
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
Absolute
IRIs
</a>
may
also
be
used
in
the
key
position
in
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 42</span>: Associating context definitions with absolute IRIs</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
    &quot;name&quot;: &quot;foaf:name&quot;,
    &quot;foaf:age&quot;:
    {
      &quot;@id&quot;: &quot;foaf:age&quot;,
      &quot;@type&quot;: &quot;xsd:integer&quot;
    },
    &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;:
    {
      &quot;@type&quot;: &quot;@id&quot;
    }
  },
  ...
}
</pre>
</div>
<p>
In
order
for
the
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
to
match
above,
the
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
<del class="diff-old">must
also
</del>
<ins class="diff-chg">needs
to
</ins>
be
used
in
the
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
<del class="diff-old">document.
</del>
<ins class="diff-chg">document
</ins></a>.
Also
note
that
<code>
foaf:homepage
</code>
will
not
use
the
<code>
{
&quot;@type&quot;:
&quot;@id&quot;
}
</code>
declaration
because
<code>
foaf:homepage
</code>
is
not
the
same
as
<code>
http://xmlns.com/foaf/0.1/homepage
</code>.
That
is,
<del class="diff-old">a
JSON-LD
processor
will
use
direct
string
comparison
when
looking
up
</del>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
</del>
<ins class="diff-chg">are
looked
up
</ins>
in
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
<ins class="diff-new">using
direct
string
comparison
</ins>
before
<del class="diff-old">it
applies
</del>
the
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
prefix
</a>
lookup
<del class="diff-old">mechanism.
</del>
<ins class="diff-chg">mechanism
is
applied.
</ins>
</p>
<p>
The
only
exception
for
using
terms
in
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
is
that
<del class="diff-old">they
must
not
be
used
in
a
</del>
circular
<del class="diff-old">manner.
</del>
<ins class="diff-chg">definitions
are
not
allowed.
</ins>
That
is,
a
definition
of
<em>
term-1
</em>
<del class="diff-old">must
not
</del>
<ins class="diff-chg">cannot
</ins>
depend
on
the
definition
of
<em>
term-2
</em>
if
<em>
term-2
</em>
also
depends
on
<em>
term-1
</em>.
For
example,
the
following
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
definition
is
illegal:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 43</span>: Illegal circular definition of terms within a context</div><pre class="example">{
  &quot;@context&quot;:
  {
    <span class="diff">&quot;term1&quot;: &quot;term2:foo&quot;,
    &quot;term2&quot;: &quot;term1:bar&quot;</span>
  },
  ...
}
</pre>
</div>
</section>
<section id="sets-and-lists">
<h3>
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
Sets
and
Lists
</h3>
<p>
A
JSON-LD
author
can
express
multiple
values
in
a
compact
way
by
using
<a class="tref internalDFN" title="array" href="#dfn-array">
<del class="diff-old">array
s.
</del>
<ins class="diff-chg">arrays
</ins></a>.
Since
graphs
do
not
describe
ordering
for
links
between
nodes,
arrays
in
JSON-LD
do
not
provide
an
ordering
of
the
contained
elements
by
default.
This
is
exactly
the
opposite
from
regular
JSON
arrays,
which
are
ordered
by
default.
For
example,
consider
the
following
simple
document:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 44</span>: Multiple values with no inherent order</div><pre class="example">{
...
  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
  &quot;nick&quot;: <span class="diff">[ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]</span>,
...
}
</pre>
</div>
<p>
The
markup
shown
above
would
result
in
the
following
data
being
generated,
each
relating
the
node
to
an
individual
value,
with
no
inherent
order:
</p>
<table class="example">
<thead>
<tr>
<th>
Subject
</th>
<th>
Property
</th>
<th>
Object
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
http://example.org/people#joebob
</td>
<td>
http://xmlns.com/foaf/0.1/nick
</td>
<td>
joe
</td>
</tr>
<tr>
<td>
http://example.org/people#joebob
</td>
<td>
http://xmlns.com/foaf/0.1/nick
</td>
<td>
bob
</td>
</tr>
<tr>
<td>
http://example.org/people#joebob
</td>
<td>
http://xmlns.com/foaf/0.1/nick
</td>
<td>
jaybee
</td>
</tr>
</tbody>
</table>
<p>
Multiple
values
may
also
be
expressed
using
the
expanded
form:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 45</span>: Using an expanded form to set multiple values</div><pre class="example">{
  &quot;@id&quot;: &quot;http://example.org/articles/8&quot;,
  &quot;dc:title&quot;: <span class="diff">
  [
    {
      &quot;@value&quot;: &quot;Das Kapital&quot;,
      &quot;@language&quot;: &quot;de&quot;
    },
    {
      &quot;@value&quot;: &quot;Capital&quot;,
      &quot;@language&quot;: &quot;en&quot;
    }
  ]</span>
}
</pre>
</div>
<p>
The
markup
shown
above
would
generate
the
following
data,
again
with
no
inherent
order:
</p>
<table class="example">
<thead>
<tr>
<th>
Subject
</th>
<th>
Property
</th>
<th>
Object
</th>
<th>
Language
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
http://example.org/articles/8
</td>
<td>
http://purl.org/dc/terms/title
</td>
<td>
Das
Kapital
</td>
<td>
de
</td>
</tr>
<tr>
<td>
http://example.org/articles/8
</td>
<td>
http://purl.org/dc/terms/title
</td>
<td>
Capital
</td>
<td>
en
</td>
</tr>
</tbody>
</table>
<p>
As
the
notion
of
ordered
collections
is
rather
important
in
data
modeling,
it
is
useful
to
have
specific
language
support.
In
JSON-LD,
a
list
may
be
represented
using
the
<code>
@list
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
as
follows:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 46</span>: An ordered collection of values in JSON-LD</div><pre class="example">{
...
  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
  &quot;foaf:nick&quot;:
  <span class="diff">{
    &quot;@list&quot;: [ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]
  }</span>,
...
}
</pre>
</div>
<p>
This
describes
the
use
of
this
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
as
being
ordered,
and
order
is
maintained
when
processing
a
document.
If
every
use
of
a
given
multi-valued
property
is
a
list,
this
may
be
abbreviated
by
setting
<code>
@container
</code>
to
<code>
@list
</code>
in
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 47</span>: Specifying that a collection is ordered in the context</div><pre class="example">{
  <span class="diff">&quot;@context&quot;:
  {
    ...
    &quot;nick&quot;:
    {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/nick&quot;,
      &quot;@container&quot;: &quot;@list&quot;
    }
  }</span>,
...
  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
  &quot;nick&quot;: <span class="diff">[ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]</span>,
...
}
</pre>
</div>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
List
of
lists
are
not
allowed
in
this
version
of
JSON-LD.
<del class="diff-old">If
a
list
of
lists
is
detected,
a
JSON-LD
processor
will
throw
an
exception.
</del>
This
decision
was
made
due
to
the
extreme
amount
of
added
complexity
when
processing
lists
of
lists.
</p>
</div>
<p>
Similarly
to
<code>
@list
</code>,
there
exists
the
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
<code>
@set
</code>
to
describe
unordered
sets.
While
its
use
in
the
body
of
a
JSON-LD
document
represents
just
syntactic
sugar
<del class="diff-old">that
must
be
</del>
optimized
away
when
processing
the
document,
it
is
very
helpful
when
used
within
the
context
of
a
document.
Values
of
terms
associated
with
a
<code>
@set
</code>
or
<code>
@list
</code>
container
are
always
represented
in
the
form
of
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
-
even
if
there
is
just
a
single
value
that
would
otherwise
be
optimized
to
a
non-array
form
in
a
<a href="#compact-document-form" class="sec-ref">
<span class="secno">
<del class="diff-old">4.15
</del>
<ins class="diff-chg">6.17
</ins>
</span>
<span class="sec-title">
Compact
Document
Form
</span>
</a>.
This
makes
post-processing
of
the
data
easier
as
the
data
is
always
in
array
form,
even
if
the
array
only
contains
a
single
value.
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
The
use
of
<code>
@container
</code>
in
the
body
of
a
JSON-LD
<del class="diff-old">document,
i.e.,
outside
@context
must
be
ignored
</del>
<ins class="diff-chg">document
has
no
meaning
and
is
not
allowed
</ins>
by
<ins class="diff-new">the
</ins>
JSON-LD
<del class="diff-old">processors.
</del>
<ins class="diff-chg">grammar
(see
</ins><a href="#json-ld-grammar" class="sec-ref"><span class="secno"><ins class="diff-chg">
B.
</ins></span><span class="sec-title"><ins class="diff-chg">
JSON-LD
Grammar
</ins></span></a><ins class="diff-chg">
).
</ins>
</p>
</div>
</section>
<section id="embedding">
<h3>
<span class="secno">
<del class="diff-old">4.10
</del>
<ins class="diff-chg">6.10
</ins>
</span>
Embedding
</h3>
<p>
<dfn title="embedding" id="dfn-embedding">
Embedding
</dfn>
is
a
JSON-LD
feature
that
allows
an
author
to
use
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definitions
</del>
<ins class="diff-chg">objects
</ins>
</a>
as
<a class="tref internalDFN" title="property" href="#dfn-property">
property
</a>
values.
This
is
a
commonly
used
mechanism
for
creating
a
parent-child
relationship
between
two
<a class="tref internalDFN" title="node" href="#dfn-node">
<del class="diff-old">node
s.
</del>
<ins class="diff-chg">nodes
</ins></a>.
</p>
<p>
The
example
shows
two
nodes
related
by
a
property
from
the
first
node:
</p>
<del class="diff-old">  {
</del>
  <div class="example"><div class="example-title"><span>Example 48</span>: Embedding a node object as property value of another node object</div><pre class="example">{
...
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;<span class="diff">knows</span>&quot;:
  {
    &quot;<span class="diff">@type</span>&quot;: &quot;<span class="diff">Person</span>&quot;,
    &quot;<span class="diff">name</span>&quot;: &quot;<span class="diff">Gregg Kellogg</span>&quot;,
  }
...
}
</pre>
</div>
<p>
A
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>,
like
the
one
used
above,
may
be
used
in
any
value
position
in
the
body
of
a
JSON-LD
document.
</p>
</section>
<section id="named-graphs">
<h3>
<span class="secno">
<del class="diff-old">4.11
</del>
<ins class="diff-chg">6.11
</ins>
</span>
Named
Graphs
</h3>
<p>
<del class="diff-old">The
@graph
keyword
</del>
<ins class="diff-chg">At
times,
it
</ins>
is
<del class="diff-old">used
</del>
<ins class="diff-chg">necessary
</ins>
to
<del class="diff-old">express
</del>
<ins class="diff-chg">make
statements
about
</ins>
a
<del class="diff-old">set
of
</del>
<a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph">
JSON-LD
<del class="diff-old">node
definition
</del>
<ins class="diff-chg">graph
</ins>
</a>
<del class="diff-old">s
that
may
not
be
directly
related
to
one
another
through
</del>
<ins class="diff-chg">itself,
rather
than
just
</ins>
a
<del class="diff-old">property.
The
mechanism
may
also
be
used
where
embedding
is
not
desirable
to
the
application.
For
example:
  {
  &quot;@context&quot;: ...,
  &quot;&quot;:
  [
    {
      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;name&quot;: &quot;Manu Sporny&quot;,
      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
    },
    {
      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
    }
  ]
}
In
this
case,
embedding
doesn't
work
as
each
</del>
<ins class="diff-chg">single
</ins><a class="tref internalDFN" title="node" href="#dfn-node">
node
<del class="diff-old">definition
references
the
other.
Using
the
@graph
keyword
allows
multiple
resources
to
be
defined
within
an
array
,
and
allows
the
use
of
a
shared
context
</del>
</a>.
<del class="diff-old">When
used
in
</del>
<ins class="diff-chg">This
can
be
done
by
grouping
</ins>
a
<del class="diff-old">JSON
object
</del>
<ins class="diff-chg">set
of
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
nodes
</ins>
</a>
<del class="diff-old">that
is
not
otherwise
a
node
definition
,
this
describes
resources
in
the
default
graph
.
This
is
equivalent
to
</del>
using
<del class="diff-old">multiple
node
definitions
in
array
and
defining
</del>
the
<code>
<del class="diff-old">@context
within
each
node
definition
:
  
  {
    
    &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
    &quot;@type&quot;: &quot;foaf:Person&quot;,
    &quot;name&quot;: &quot;Manu Sporny&quot;,
    &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
  },
  {
    
    &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
    &quot;@type&quot;: &quot;foaf:Person&quot;,
    &quot;name&quot;: &quot;Gregg Kellogg&quot;,
    &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
  }
]
JSON-LD
allows
you
to
name
things
on
the
Web
by
assigning
an
@id
</del>
<ins class="diff-chg">@graph
</ins>
</code>
<del class="diff-old">to
them,
which
is
typically
an
IRI
</del>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
<ins class="diff-chg">keyword
</ins>
</a>.
<del class="diff-old">This
notion
extends
to
the
ability
to
identify
graphs
in
the
same
manner.
</del>
A
developer
may
<ins class="diff-new">also
</ins>
name
data
expressed
using
the
<code>
@graph
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
by
pairing
it
with
an
<code>
@id
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
<del class="diff-old">.
This
enables
the
developer
to
make
statements
about
a
linked
data
graph
</del>
</a>
<del class="diff-old">itself,
rather
than
just
a
single
node
.
</del>
<ins class="diff-chg">as
shown
in
the
following
example:
</ins>
</p>
<del class="diff-old">  {
</del>
  <div class="example"><div class="example-title"><span>Example 49</span>: Identifying and making statements about a graph</div><pre class="example">{
  &quot;@context&quot;: {
<del class="diff-old">    &quot;asOf&quot;: &quot;http://purl.org/net/provenance/ns#accessedResource&quot;,
</del>
<ins class="diff-chg">    &quot;generatedAt&quot;: &quot;http://www.w3.org/ns/prov#generatedAtTime&quot;,
</ins>
    &quot;Person&quot;: &quot;http://xmlns.com/foaf/0.1/Person&quot;,
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;knows&quot;: &quot;http://xmlns.com/foaf/0.1/knows&quot;,
    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;
  },
  <span class="diff">&quot;@id&quot;: &quot;http://example.org/graphs/73&quot;,
<del class="diff-old">  &quot;asOf&quot;: { &quot;@value&quot;: &quot;2012-04-09&quot;, &quot;@type&quot;: &quot;xsd:date&quot; },
</del>
<ins class="diff-chg">  &quot;generatedAt&quot;: { &quot;@value&quot;: &quot;2012-04-09&quot;, &quot;@type&quot;: &quot;xsd:date&quot; },
</ins>
  &quot;@graph&quot;:</span>
  [
    {
      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
      &quot;@type&quot;: &quot;Person&quot;,
      &quot;name&quot;: &quot;Manu Sporny&quot;,
      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
    },
    {
      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
      &quot;@type&quot;: &quot;Person&quot;,
      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
    }
  ]
}
</pre>
</div>
<p>
The
example
above
expresses
a
<em>
named
</em>
<del class="diff-old">linked
data
</del>
<a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph">
<ins class="diff-chg">JSON-LD
</ins>
graph
</a>
that
is
identified
by
the
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
<code>
http://example.org/graphs/73
</code>.
That
graph
is
composed
of
the
statements
about
Manu
and
Gregg.
Metadata
about
the
graph
itself
is
also
expressed
via
the
<code>
<del class="diff-old">asOf
</del>
<ins class="diff-chg">generatedAt
</ins>
</code>
property,
which
specifies
when
the
<del class="diff-old">information
</del>
<ins class="diff-chg">graph
</ins>
was
<del class="diff-old">retrieved
from
the
Web.
</del>
<ins class="diff-chg">generated.
</ins>
An
alternative
view
of
the
information
above
is
represented
in
table
form
below:
</p>
<table class="example">
<thead>
<tr>
<th>
Graph
</th>
<th>
Subject
</th>
<th>
Property
</th>
<th>
Object
</th>
<th>
Datatype
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://example.org/graphs/73
</td>
<td>
<del class="diff-old">http://purl.org/net/provenance/ns#accessedResource
</del>
<ins class="diff-chg">http://www.w3.org/ns/prov#generatedAtTime
</ins>
</td>
<td>
2012-04-09
</td>
<td>
http://www.w3.org/2001/XMLSchema#date
</td>
</tr>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://manu.sporny.org/i/public
</td>
<td>
http://www.w3.org/2001/XMLSchema#type
</td>
<td>
http://xmlns.com/foaf/0.1/Person
</td>
<td>
</td>
</tr>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://manu.sporny.org/i/public
</td>
<td>
http://xmlns.com/foaf/0.1/name
</td>
<td>
Manu
Sporny
</td>
<td>
</td>
</tr>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://manu.sporny.org/i/public
</td>
<td>
http://xmlns.com/foaf/0.1/knows
</td>
<td>
http://greggkellogg.net/foaf#me
</td>
<td>
</td>
</tr>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://greggkellogg.net/foaf#me
</td>
<td>
http://www.w3.org/2001/XMLSchema#type
</td>
<td>
http://xmlns.com/foaf/0.1/Person
</td>
<td>
</td>
</tr>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://greggkellogg.net/foaf#me
</td>
<td>
http://xmlns.com/foaf/0.1/name
</td>
<td>
Gregg
Kellogg
</td>
<td>
</td>
</tr>
<tr>
<td>
http://example.org/graphs/73
</td>
<td>
http://greggkellogg.net/foaf#me
</td>
<td>
http://xmlns.com/foaf/0.1/knows
</td>
<td>
http://manu.sporny.org/i/public
</td>
<td>
</td>
</tr>
</tbody>
</table>
<p>
<ins class="diff-new">When
</ins><code><ins class="diff-new">
@graph
</ins></code><ins class="diff-new">
is
used
in
a
document's
top-level
object
which
has
no
other
</ins><a class="tref internalDFN" title="property" href="#dfn-property"><ins class="diff-new">
properties
</ins></a><ins class="diff-new">
that
are
mapped
to
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-new">
IRI
</ins></abbr></a><ins class="diff-new">
or
a
</ins><a class="tref internalDFN" title="keyword" href="#dfn-keyword"><ins class="diff-new">
keyword
</ins></a><ins class="diff-new">
it
is
considered
to
express
the
otherwise
implicit
default
graph.
This
mechanism
can
be
useful
when
a
number
of
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-new">
nodes
</ins></a><ins class="diff-new">
thay
may
not
directly
relate
to
one
another
through
a
property
or
where
</ins><a class="tref internalDFN" title="embedding" href="#dfn-embedding"><ins class="diff-new">
embedding
</ins></a><ins class="diff-new">
is
not
desirable
to
the
application.
For
example:
</ins></p>  <div class="example"><div class="example-title"><span>Example 50</span>: Using @graph to explicitly express the default graph</div><pre class="example">{<ins class="diff-new">
  &quot;@context&quot;: ...,
  &quot;<span class="diff">@graph</span>&quot;:
  [
    {
      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;name&quot;: &quot;Manu Sporny&quot;,
      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
    },
    {
      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
    }
  ]
}
</ins></pre></div><p><ins class="diff-new">
In
this
case,
embedding
doesn't
work
as
each
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a><ins class="diff-new">
references
the
other.
Using
the
</ins><code><ins class="diff-new">
@graph
</ins></code><a class="tref internalDFN" title="keyword" href="#dfn-keyword"><ins class="diff-new">
keyword
</ins></a><ins class="diff-new">
allows
multiple
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-new">
nodes
</ins></a><ins class="diff-new">
to
be
defined
within
an
</ins><a class="tref internalDFN" title="array" href="#dfn-array"><ins class="diff-new">
array
</ins></a>,<ins class="diff-new">
and
allows
the
use
of
a
shared
</ins><a class="tref internalDFN" title="context" href="#dfn-context"><ins class="diff-new">
context
</ins></a>.<ins class="diff-new">
This
is
equivalent
to
using
multiple
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
objects
</ins></a><ins class="diff-new">
in
array
and
defining
the
</ins><code><ins class="diff-new">
@context
</ins></code><ins class="diff-new">
within
each
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a>:</p>  <div class="example"><div class="example-title"><span>Example 51</span>: Context needs to be duplicated if @graph is not used</div><pre class="example">[<ins class="diff-new">
  {
</ins>    <span class="diff">&quot;@context&quot;: ...,</span><ins class="diff-new">
    &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
    &quot;@type&quot;: &quot;foaf:Person&quot;,
    &quot;name&quot;: &quot;Manu Sporny&quot;,
    &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
  },
  {
</ins>    <span class="diff">&quot;@context&quot;: ...,</span><ins class="diff-new">
    &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
    &quot;@type&quot;: &quot;foaf:Person&quot;,
    &quot;name&quot;: &quot;Gregg Kellogg&quot;,
    &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
  }
]
</ins></pre></div>
</section>
<section id="identifying-blank-nodes">
<h3>
<span class="secno">
<del class="diff-old">4.12
</del>
<ins class="diff-chg">6.12
</ins>
</span>
Identifying
<del class="diff-old">Unlabeled
</del>
<ins class="diff-chg">Blank
</ins>
Nodes
</h3>
<p>
At
times,
it
becomes
necessary
to
be
able
to
express
information
without
being
able
to
specify
the
node.
<del class="diff-old">Typically,
this
</del>
<ins class="diff-chg">This
</ins>
type
of
node
is
called
<del class="diff-old">an
unlabeled
node
or
</del>
a
<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
blank
node
<del class="diff-old">(see
[
RDF-CONCEPTS
</del>
</a>
<del class="diff-old">]
</del>
<ins class="diff-chg">(see
</ins>
<cite>
<a href="http://www.w3.org/TR/rdf11-concepts/#section-blank-nodes">
Section
3.4:
Blank
Nodes
</a>
</cite>
<del class="diff-old">).
</del>
<ins class="diff-chg">of
[
</ins><cite><a class="bibref" href="#bib-RDF-CONCEPTS"><ins class="diff-chg">
RDF-CONCEPTS
</ins></a></cite><ins class="diff-chg">
]).
</ins>
In
JSON-LD,
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier">
<ins class="diff-chg">blank
</ins>
node
identifiers
</a>
are
automatically
created
if
a
node
is
not
specified
using
the
<code>
@id
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>.
However,
authors
may
provide
identifiers
for
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
<ins class="diff-chg">blank
</ins>
nodes
</a>
by
using
the
special
<code>
_
</code>
(underscore)
<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
prefix
</a>.
This
allows
one
to
reference
the
node
locally
within
the
document,
but
makes
it
impossible
to
reference
the
node
from
an
external
document.
The
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier">
<ins class="diff-chg">blank
</ins>
node
identifier
</a>
is
scoped
to
the
document
in
which
it
is
used.
</p>
<del class="diff-old">{
</del>
  <div class="example"><div class="example-title"><span>Example 52</span>: Specifying a local blank node identifier</div><pre class="example">{
...
  &quot;@id&quot;: &quot;<span class="diff">_:foo</span>&quot;,
...
}
</pre>
</div>
<p>
The
example
above
would
set
the
node
to
<code>
_:foo
</code>,
which
can
then
be
used
elsewhere
in
the
JSON-LD
document
to
refer
back
to
the
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
<ins class="diff-chg">blank
</ins>
node
</a>.
If
a
developer
finds
that
they
refer
to
the
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
<ins class="diff-chg">blank
</ins>
node
</a>
more
than
once,
they
should
consider
naming
the
node
using
a
<del class="diff-old">de-referenceable
</del>
<ins class="diff-chg">dereferenceable
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
so
that
it
can
<ins class="diff-new">also
</ins>
be
referenced
<del class="diff-old">also
</del>
from
other
documents.
</p>
</section>
<section id="aliasing-keywords">
<h3>
<span class="secno">
<del class="diff-old">4.13
</del>
<ins class="diff-chg">6.13
</ins>
</span>
Aliasing
Keywords
</h3>
<p>
Each
of
the
JSON-LD
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keywords
</a>,
except
for
<code>
@context
</code>,
may
be
aliased
to
application-specific
keywords.
This
feature
allows
legacy
JSON
content
to
be
utilized
by
JSON-LD
by
re-using
JSON
keys
that
already
exist
in
legacy
documents.
This
feature
also
allows
developers
to
design
domain-specific
implementations
using
only
the
JSON-LD
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 53</span>: Aliasing keywords</div><pre class="example">{
  &quot;@context&quot;:
  {
     <span class="diff">&quot;url&quot;: &quot;@id&quot;</span>,
     <span class="diff">&quot;a&quot;: &quot;@type&quot;</span>,
     &quot;name&quot;: &quot;http://schema.org/name&quot;
  },
  &quot;<span class="diff">url</span>&quot;: &quot;http://example.com/about#gregg&quot;,
  &quot;<span class="diff">a</span>&quot;: &quot;http://schema.org/Person&quot;,
  &quot;name&quot;: &quot;Gregg Kellogg&quot;
}
</pre>
</div>
<p>
In
the
example
above,
the
<code>
@id
</code>
and
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keywords
</a>
have
been
given
the
aliases
<strong>
url
</strong>
and
<strong>
a
</strong>,
respectively.
</p>
</section>
<section id="data-annotations">
<h3>
<span class="secno">
<ins class="diff-new">6.14
</ins></span><ins class="diff-new">
Data
Annotations
</ins></h3><p><ins class="diff-new">
It
is
common
for
developers
using
JSON
to
organize
their
data
in
ways
that
makes
working
with
the
data
more
efficient.
It
is
often
that
these
methods
of
organizing
data
are
not
meant
to
express
Linked
Data,
but
should
survive
transformation
by
JSON-LD.
For
example,
if
a
developer
organizes
employees
in
a
JSON-LD
document
by
a
company-issued
ID
number,
JSON-LD
should
not
destroy
that
'database
index'
when
transforming
the
data.
Data
annotations
allow
content
that
would
otherwise
be
removed
from
a
JSON-LD
graph
to
be
preserved
by
instructing
the
JSON-LD
processor
to
syntactically
preserve
the
annotation
information
and
continue
processing
deeper
into
the
JSON
data
structure.
</ins></p><div class="example"><div class="example-title"><span>Example 54</span>: Data annotations</div><pre class="example">{<ins class="diff-new">
  &quot;@context&quot;:
  {
     &quot;schema&quot;: &quot;http://schema.org/&quot;,
     &quot;Article&quot;: &quot;schema:Blog&quot;,
     &quot;name&quot;: &quot;schema:name&quot;,
     &quot;articleBody&quot;: &quot;schema:articleBody&quot;,
     &quot;wordCount&quot;: &quot;schema:wordCount&quot;,
     &quot;commentCount&quot;: &quot;http://example.com/schema/wordCount&quot;,
     &quot;blogPost&quot;: {
       &quot;@id&quot;: &quot;schema:blogPost&quot;,
</ins>       <span class="diff">&quot;@container&quot;: &quot;@annotation&quot;</span><ins class="diff-new">
  },
  &quot;@id&quot;: &quot;http://example.com/&quot;,
  &quot;@type&quot;: &quot;Blog&quot;,
  &quot;name&quot;: &quot;World Financial News&quot;,
</ins>  <span class="diff">&quot;blogPost&quot;: {<ins class="diff-new">
     &quot;en&quot;: {
       &quot;@id&quot;: &quot;http://example.com/posts/1/en&quot;,
       &quot;articleBody&quot;: &quot;World commodities were up today with heavy trading of crude oil...&quot;,
       &quot;wordCount&quot;: 1539,
       &quot;commentCount&quot;: 64
     },
     &quot;de&quot;: {
       &quot;@id&quot;: &quot;http://example.com/posts/1/de&quot;,
       &quot;articleBody&quot;: &quot;Welt Rohstoffe waren bis heute mit schweren Handel mit Rohöl...&quot;,
       &quot;wordCount&quot;: 1204,
       &quot;commentCount&quot;: 23
     }</span>
  }
}
</ins></pre></div><p><ins class="diff-new">
In
the
example
above,
the
</ins><strong><ins class="diff-new">
blogPost
</ins></strong><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><ins class="diff-new">
has
been
marked
as
a
</ins><em><ins class="diff-new">
data
annotation
container
</ins></em>.<ins class="diff-new">
The
</ins><strong><ins class="diff-new">
en
</ins></strong>,<strong><ins class="diff-new">
de
</ins></strong>,<ins class="diff-new">
and
</ins><strong><ins class="diff-new">
ja
</ins></strong><ins class="diff-new">
keys
will
effectively
be
ignored
semantically,
but
preserved
syntactically,
by
the
JSON-LD
Processor
as
</ins><em><ins class="diff-new">
annotations
</ins></em>.<ins class="diff-new">
The
interpretation
of
the
data
above
is
expressed
in
the
table
below.
Note
how
the
annotations
do
not
appear
in
the
Linked
Data
below,
but
would
continue
to
exist
if
the
document
were
compacted
or
expanded
using
a
JSON-LD
processor:
</ins></p><table class="example"><thead><tr><th><ins class="diff-new">
Subject
</ins></th><th><ins class="diff-new">
Property
</ins></th><th><ins class="diff-new">
Object
</ins></th><th><ins class="diff-new">
Datatype
</ins></th></tr></thead><tbody><tr><td><ins class="diff-new">
http://example.com/
</ins></td><td><ins class="diff-new">
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
</ins></td><td><ins class="diff-new">
http://schema.org/Blog
</ins></td><td></td></tr><tr><td><ins class="diff-new">
http://example.com/
</ins></td><td><ins class="diff-new">
http://schema.org/name
</ins></td><td><ins class="diff-new">
World
Financial
News
</ins></td><td></td></tr><tr><td><ins class="diff-new">
http://example.com/
</ins></td><td><ins class="diff-new">
http://schema.org/blogPost
</ins></td><td><ins class="diff-new">
http://example.com/posts/1/en
</ins></td><td></td></tr><tr><td><ins class="diff-new">
http://example.com/
</ins></td><td><ins class="diff-new">
http://schema.org/blogPost
</ins></td><td><ins class="diff-new">
http://example.com/posts/1/de
</ins></td><td></td></tr><tr><td><ins class="diff-new">
http://example.com/posts/1/en
</ins></td><td><ins class="diff-new">
http://schema.org/articleBody
</ins></td><td><ins class="diff-new">
World
commodities
were
up
today
with
heavy
trading
of
crude
oil...
</ins></td><td></td></tr><tr><td><ins class="diff-new">
http://example.com/posts/1/en
</ins></td><td><ins class="diff-new">
http://schema.org/wordCount
</ins></td><td><ins class="diff-new">
1539
</ins></td><td><ins class="diff-new">
http://www.w3.org/2001/XMLSchema#integer
</ins></td></tr><tr><td><ins class="diff-new">
http://example.com/posts/1/en
</ins></td><td><ins class="diff-new">
http://example.com/schema/commentCount
</ins></td><td><ins class="diff-new">
64
</ins></td><td><ins class="diff-new">
http://www.w3.org/2001/XMLSchema#integer
</ins></td></tr><tr><td><ins class="diff-new">
http://example.com/posts/1/de
</ins></td><td><ins class="diff-new">
http://schema.org/articleBody
</ins></td><td><ins class="diff-new">
Welt
Rohstoffe
waren
bis
heute
mit
schweren
Handel
mit
Rohöl...
</ins></td><td></td></tr><tr><td><ins class="diff-new">
http://example.com/posts/1/de
</ins></td><td><ins class="diff-new">
http://schema.org/wordCount
</ins></td><td><ins class="diff-new">
1204
</ins></td><td><ins class="diff-new">
http://www.w3.org/2001/XMLSchema#integer
</ins></td></tr><tr><td><ins class="diff-new">
http://example.com/posts/1/de
</ins></td><td><ins class="diff-new">
http://example.com/schema/commentCount
</ins></td><td><ins class="diff-new">
23
</ins></td><td><ins class="diff-new">
http://www.w3.org/2001/XMLSchema#integer
</ins></td></tr></tbody></table></section><section id="explicitly-ignoring-data"><h3><span class="secno"><ins class="diff-new">
6.15
</ins></span><ins class="diff-new">
Explicitly
Ignoring
Data
</ins></h3><p><ins class="diff-new">
At
times,
it
becomes
necessary
to
explicitly
ignore
data
expressed
in
JSON
documents
because
it
has
no
semantic
meaning.
For
example,
when
the
</ins><code><ins class="diff-new">
@vocab
</ins></code><ins class="diff-new">
keyword
is
used,
every
key
in
a
JSON-LD
object
is
appended
to
the
vocabulary
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-new">
IRI
</ins></abbr></a>.<ins class="diff-new">
The
author
may
not
want
that
behavior
to
apply
to
every
key,
and
it
may
be
easier
to
specify
just
the
keys
that
they
want
the
JSON-LD
processor
to
ignore.
For
this
purpose,
an
author
may
associate
the
</ins><a class="tref internalDFN" title="null" href="#dfn-null"><ins class="diff-new">
null
</ins></a><ins class="diff-new">
keyword
with
a
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><ins class="diff-new">
in
the
JSON-LD
Context.
</ins></p><div class="example"><div class="example-title"><span>Example 55</span>: Using the null keyword to ignore data</div><pre class="example">{<ins class="diff-new">
  &quot;@context&quot;:
  {
     &quot;@vocab&quot;: &quot;http://schema.org/&quot;,
</ins>     <span class="diff">&quot;databaseId&quot;: null</span><ins class="diff-new">
  },
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;description&quot;: &quot;That guy&quot;,
  &quot;gender&quot;: &quot;Male&quot;,
</ins>  <span class="diff">&quot;databaseId&quot;: &quot;23987520&quot;</span><ins class="diff-new">
}
</ins></pre></div><p><ins class="diff-new">
In
the
example
above,
the
author
has
used
</ins><code><ins class="diff-new">
@vocab
</ins></code><ins class="diff-new">
as
the
base
</ins><abbr title="Internationalized Resource Identifier"><ins class="diff-new">
IRI
</ins></abbr><ins class="diff-new">
for
all
terms
in
the
document,
but
has
expressed
that
the
</ins><code><ins class="diff-new">
databaseId
</ins></code><ins class="diff-new">
value
should
not
be
processed
by
the
JSON-LD
processor
by
associating
it
with
the
</ins><a class="tref internalDFN" title="null" href="#dfn-null"><ins class="diff-new">
null
</ins></a><ins class="diff-new">
keyword
in
the
JSON-LD
Context.
</ins></p></section>
<section id="expanded-document-form">
<h3>
<span class="secno">
<del class="diff-old">4.14
</del>
<ins class="diff-chg">6.16
</ins>
</span>
Expanded
Document
Form
</h3>
<p>
The
JSON-LD
API
[
<cite>
<a class="bibref" href="#bib-JSON-LD-API">
JSON-LD-API
</a>
</cite>
]
defines
an
method
for
<em>
expanding
</em>
a
JSON-LD
document.
Expansion
is
the
process
of
taking
a
JSON-LD
document
and
applying
a
<code>
@context
</code>
such
that
all
IRIs,
types,
and
values
are
expanded
so
that
the
<code>
@context
</code>
is
no
longer
necessary.
</p>
<p>
For
example,
assume
the
following
JSON-LD
input
document:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 56</span>: Sample JSON-LD document</div><pre class="example">{
   &quot;@context&quot;:
   {
      &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
      &quot;homepage&quot;: {
        &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
        &quot;@type&quot;: &quot;@id&quot;
      }
   },
   &quot;name&quot;: &quot;Manu Sporny&quot;,
   &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
}
</pre>
</div>
<p>
Running
the
JSON-LD
Expansion
algorithm
against
the
JSON-LD
input
document
provided
above
would
result
in
the
following
output:
</p>
<del class="diff-old">[
</del>
<div class="example"><div class="example-title"><span>Example 57</span>: Expanded form for the previous example</div><pre class="example">[
  {
    &quot;http://xmlns.com/foaf/0.1/name&quot;: [
      { &quot;@value&quot;: &quot;Manu Sporny&quot; }
    ],
    &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [
      { &quot;@id&quot;: &quot;http://manu.sporny.org/&quot; }
    ]
  }
]
</pre>
</div>
<p>
Expanded
document
form
is
useful
when
an
application
has
to
process
input
data
in
a
deterministic
form.
It
has
been
optimized
to
ensure
that
the
code
that
developers
have
to
write
is
minimized
compared
to
the
code
that
would
have
to
be
written
to
operate
on
<a href="#compact-document-form" class="sec-ref">
<span class="secno">
<del class="diff-old">4.15
</del>
<ins class="diff-chg">6.17
</ins>
</span>
<span class="sec-title">
Compact
Document
Form
</span>
</a>.
</p>
</section>
<section id="compact-document-form">
<h3>
<span class="secno">
<del class="diff-old">4.15
</del>
<ins class="diff-chg">6.17
</ins>
</span>
Compact
Document
Form
</h3>
<p>
The
JSON-LD
API
[
<cite>
<a class="bibref" href="#bib-JSON-LD-API">
JSON-LD-API
</a>
</cite>
]
defines
a
method
for
<em>
compacting
</em>
a
JSON-LD
document.
Compaction
is
the
process
of
taking
a
JSON-LD
document
and
applying
a
context
such
that
the
most
compact
form
of
the
document
is
generated.
JSON
is
typically
expressed
in
a
very
compact,
key-value
format.
That
is,
full
IRIs
are
rarely
used
as
keys.
At
times,
a
JSON-LD
document
may
be
received
that
is
not
in
its
most
compact
form.
JSON-LD,
via
the
API,
provides
a
way
to
compact
a
JSON-LD
document.
</p>
<p>
For
example,
assume
the
following
JSON-LD
input
document:
</p>
<del class="diff-old">[
</del>
<div class="example"><div class="example-title"><span>Example 58</span>: Sample expanded JSON-LD document</div><pre class="example">[
  {
    &quot;http://xmlns.com/foaf/0.1/name&quot;: [ &quot;Manu Sporny&quot; ],
    &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [
      {
       &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
      }
    ]
  }
]
</pre>
</div>
<p>
Additionally,
assume
the
following
developer-supplied
JSON-LD
context:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 59</span>: Sample context</div><pre class="example">{
  &quot;@context&quot;: {
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;homepage&quot;: {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    }
  }
}
</pre>
</div>
<p>
Running
the
JSON-LD
Compaction
algorithm
given
the
context
supplied
above
against
the
JSON-LD
input
document
provided
above
would
result
in
the
following
output:
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 60</span>: Compact form of the sample document once sample context has been applied</div><pre class="example">{
  &quot;@context&quot;: {
    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
    &quot;homepage&quot;: {
      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    }
  },
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
}
</pre>
</div>
<p>
The
compaction
algorithm
enables
a
developer
to
map
any
document
into
an
application-specific
compacted
form
by
first
<a href="#expanded-document-form" class="sec-ref">
<span class="secno">
<del class="diff-old">4.14
</del>
<ins class="diff-chg">6.16
</ins>
</span>
<span class="sec-title">
Expanded
Document
Form
</span>
</a>.
While
the
context
provided
above
mapped
<code>
http://xmlns.com/foaf/0.1/name
</code>
to
<strong>
name
</strong>,
it
could
have
also
mapped
it
to
any
arbitrary
string
provided
by
the
developer.
This
powerful
<del class="diff-old">mechanism,
along
with
another
JSON-LD
API
technique
called
framing
,
</del>
<ins class="diff-chg">mechanism
</ins>
allows
the
developer
to
re-shape
the
incoming
JSON
data
into
a
format
that
is
optimized
for
their
application.
</p>
</section>
</section>
<section class="appendix normative" id="data-model">
<h2>
<span class="secno">
A.
</span>
<del class="diff-old">JSON-LD
Grammar
</del>
<ins class="diff-chg">Data
Model
</ins>
</h2>
<del class="diff-old">This
section
is
normative
This
section
</del>
<p>
<ins class="diff-chg">JSON-LD
</ins>
is
<del class="diff-old">an
attempt
to
formalize
</del>
a
<del class="diff-old">normative
grammar
</del>
<ins class="diff-chg">serialization
format
</ins>
for
<del class="diff-old">JSON-LD.
This
appendix
restates
</del>
<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
<ins class="diff-chg">Linked
Data
</ins></a><ins class="diff-chg">
based
on
JSON.
It
is
therefore
important
to
distinguish
between
</ins>
the
<del class="diff-old">syntactic
conventions
described
</del>
<ins class="diff-chg">syntax,
which
is
defined
by
JSON
</ins>
in
<del class="diff-old">the
previous
sections
more
formally.
</del>
<ins class="diff-chg">[
</ins><cite><a class="bibref" href="#bib-RFC4627"><ins class="diff-chg">
RFC4627
</ins></a></cite><ins class="diff-chg">
],
and
</ins><dfn title="json-ld_data_model" id="dfn-json-ld_data_model"><ins class="diff-chg">
JSON-LD's
data
model
</ins></dfn><ins class="diff-chg">
which
is
defined
as
follows:
</ins>
</p>
<ul>
<li>
A
<dfn title="json-ld_document" id="dfn-json-ld_document">
JSON-LD
<del class="diff-old">processor
</del>
<ins class="diff-chg">document
</ins></dfn><ins class="diff-chg">
serializes
a
collection
of
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-chg">
JSON-LD
graphs
</ins></a><ins class="diff-chg">
and
comprises
exactly
one
</ins><dfn title="default_graph" id="dfn-default_graph"><ins class="diff-chg">
default
graph
</ins></dfn><ins class="diff-chg">
and
zero
or
more
</ins><dfn title="named_graph" id="dfn-named_graph"><ins class="diff-chg">
named
graphs
</ins></dfn>.</li><li><ins class="diff-chg">
The
default
graph
does
not
have
a
name
and
</ins><em class="rfc2119" title="may"><ins class="diff-chg">
may
</ins></em><ins class="diff-chg">
be
empty.
</ins></li><li><ins class="diff-chg">
Each
named
graph
is
a
pair
consisting
of
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a><ins class="diff-chg">
or
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
node
</ins></a><ins class="diff-chg">
(the
</ins><dfn title="graph_name" id="dfn-graph_name"><ins class="diff-chg">
graph
name
</ins></dfn><ins class="diff-chg">
)
and
a
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-chg">
JSON-LD
graph
</ins></a>.<ins class="diff-chg">
Whenever
possible,
the
</ins><a class="tref internalDFN" title="graph_name" href="#dfn-graph_name"><ins class="diff-chg">
graph
name
</ins></a>
<em class="rfc2119" title="should">
should
</em>
<del class="diff-old">attempt
to
process
non-conforming
</del>
<ins class="diff-chg">be
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a>.</li><li><ins class="diff-chg">
A
</ins><dfn title="json-ld_graph" id="dfn-json-ld_graph">
JSON-LD
<del class="diff-old">documents.
Conformance
violations
</del>
<ins class="diff-chg">graph
</ins></dfn><ins class="diff-chg">
is
a
labeled
directed
graph,
i.e.,
a
set
of
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
nodes
</ins></a><ins class="diff-chg">
connected
by
</ins><a class="tref internalDFN" title="edge" href="#dfn-edge"><ins class="diff-chg">
edges
</ins></a>.</li><li><ins class="diff-chg">
Every
</ins><dfn title="edge" id="dfn-edge"><ins class="diff-chg">
edge
</ins></dfn><ins class="diff-chg">
has
a
direction
associated
with
it
and
is
labeled
with
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a><ins class="diff-chg">
or
a
</ins><a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier"><ins class="diff-chg">
blank
node
identifier
</ins></a>.<ins class="diff-chg">
Within
the
JSON-LD
syntax
these
edge
labels
are
called
</ins><dfn title="property" id="dfn-property"><ins class="diff-chg">
properties
</ins></dfn>.<ins class="diff-chg">
Whenever
possible,
an
</ins><a class="tref internalDFN" title="edge" href="#dfn-edge"><ins class="diff-chg">
edge
</ins></a><em class="rfc2119" title="should"><ins class="diff-chg">
should
</ins></em><ins class="diff-chg">
be
labeled
with
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a>.</li><li><ins class="diff-chg">
Every
</ins><dfn title="node" id="dfn-node"><ins class="diff-chg">
node
</ins></dfn><ins class="diff-chg">
is
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a>,<ins class="diff-chg">
a
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
node
</ins></a>,<ins class="diff-chg">
a
</ins><a class="tref internalDFN" title="json-ld_value" href="#dfn-json-ld_value"><ins class="diff-chg">
JSON-LD
value
</ins></a>,<ins class="diff-chg">
or
a
</ins><a class="tref internalDFN" title="list" href="#dfn-list"><ins class="diff-chg">
list
</ins></a>.</li><li><ins class="diff-chg">
A
node
having
an
outgoing
edge
</ins>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">reported
through
</del>
<ins class="diff-chg">an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a><ins class="diff-chg">
or
</ins>
a
<del class="diff-old">conformance
violation
callback
mechanism
</del>
<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
<ins class="diff-chg">blank
node
</ins></a>.</li><li><ins class="diff-chg">
A
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-chg">
JSON-LD
graph
</ins></a><em class="rfc2119" title="should not"><ins class="diff-chg">
should
not
</ins></em><ins class="diff-chg">
contain
unconnected
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
nodes
</ins></a>,<ins class="diff-chg">
i.e.,
nodes
which
are
not
connected
by
an
</ins><a class="tref internalDFN" title="edge" href="#dfn-edge"><ins class="diff-chg">
edge
</ins></a><ins class="diff-chg">
to
any
other
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
node
</ins></a>.</li><li><ins class="diff-chg">
An
</ins><dfn title="iri" id="dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></dfn><ins class="diff-chg">
(Internationalized
Resource
Identifier)
is
a
string
that
conforms
to
the
syntax
</ins>
defined
in
<del class="diff-old">the
</del>
[
<cite>
<del class="diff-old">JSON-LD-API
</del>
<a class="bibref" href="#bib-RFC3987">
<ins class="diff-chg">RFC3987
</ins>
</a>
</cite>
].
<del class="diff-old">For
</del>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<ins class="diff-chg">IRIs
</ins></a><ins class="diff-chg">
used
within
</ins>
a
<a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph">
JSON-LD
<ins class="diff-new">graph
</ins></a><em class="rfc2119" title="should"><ins class="diff-new">
should
</ins></em><ins class="diff-new">
return
a
</ins><a class="tref internalDFN" title="linked_data" href="#dfn-linked_data"><ins class="diff-new">
Linked
Data
</ins></a>
document
<del class="diff-old">to
</del>
<ins class="diff-chg">describing
the
resource
denoted
by
that
</ins><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr><ins class="diff-chg">
when
being
dereferenced.
</ins></li><li><ins class="diff-chg">
A
</ins><dfn title="blank_node" id="dfn-blank_node"><ins class="diff-chg">
blank
node
</ins></dfn><ins class="diff-chg">
is
a
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
node
</ins></a><ins class="diff-chg">
which
is
neither
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a>,<ins class="diff-chg">
nor
a
</ins><a class="tref internalDFN" title="json-ld_value" href="#dfn-json-ld_value"><ins class="diff-chg">
JSON-LD
value
</ins></a>,<ins class="diff-chg">
or
a
</ins><a class="tref internalDFN" title="list" href="#dfn-list"><ins class="diff-chg">
list
</ins></a>.<ins class="diff-chg">
A
blank
node
</ins><em class="rfc2119" title="may"><ins class="diff-chg">
may
</ins></em>
be
<del class="diff-old">conforming,
it
</del>
<ins class="diff-chg">identified
by
a
</ins><a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier"><ins class="diff-chg">
blank
node
identifier
</ins></a>.</li><li><ins class="diff-chg">
A
</ins><dfn title="blank_node_identifier" id="dfn-blank_node_identifier"><ins class="diff-chg">
blank
node
identifier
</ins></dfn><ins class="diff-chg">
is
a
string
that
can
be
used
as
an
identifier
for
a
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
node
</ins></a><ins class="diff-chg">
within
the
scope
of
a
</ins><a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document"><ins class="diff-chg">
JSON-LD
document
</ins></a>.<ins class="diff-chg">
Blank
node
identifiers
begin
with
</ins><code><ins class="diff-chg">
_:
</ins></code>.</li><li><ins class="diff-chg">
A
</ins><dfn title="json-ld_value" id="dfn-json-ld_value"><ins class="diff-chg">
JSON-LD
value
</ins></dfn><ins class="diff-chg">
is
a
</ins><a class="tref internalDFN" title="string" href="#dfn-string"><ins class="diff-chg">
string
</ins></a>,<ins class="diff-chg">
a
</ins><a class="tref internalDFN" title="number" href="#dfn-number"><ins class="diff-chg">
number
</ins></a>,<a class="tref internalDFN" title="true" href="#dfn-true"><ins class="diff-chg">
true
</ins></a><ins class="diff-chg">
or
</ins><a class="tref internalDFN" title="false" href="#dfn-false"><ins class="diff-chg">
false
</ins></a>,<ins class="diff-chg">
a
</ins><a class="tref internalDFN" title="typed_value" href="#dfn-typed_value"><ins class="diff-chg">
typed
value
</ins></a>,<ins class="diff-chg">
or
a
</ins><a class="tref internalDFN" title="language-tagged_string" href="#dfn-language-tagged_string"><ins class="diff-chg">
language-tagged
string
</ins></a>.</li><li><ins class="diff-chg">
A
</ins><dfn title="typed_value" id="dfn-typed_value"><ins class="diff-chg">
typed
value
</ins></dfn><ins class="diff-chg">
consists
of
a
value,
which
is
a
string,
and
a
type,
which
is
an
</ins><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr>.</li><li><ins class="diff-chg">
A
</ins><dfn title="language-tagged_string" id="dfn-language-tagged_string"><ins class="diff-chg">
language-tagged
string
</ins></dfn><ins class="diff-chg">
consists
of
a
string
and
a
non-empty
language
tag
as
defined
by
[
</ins><cite><a class="bibref" href="#bib-BCP47"><ins class="diff-chg">
BCP47
</ins></a></cite><ins class="diff-chg">
].
The
language
tag
must
be
well-formed
according
to
section
</ins><a href="http://tools.ietf.org/html/bcp47#section-2.2.9"><ins class="diff-chg">
2.2.9
</ins></a><ins class="diff-chg">
of
[
</ins><cite><a class="bibref" href="#bib-BCP47"><ins class="diff-chg">
BCP47
</ins></a></cite><ins class="diff-chg">
],
and
</ins>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">a
valid
JSON
document
</del>
<ins class="diff-chg">normalized
to
lowercase.
</ins></li><li><ins class="diff-chg">
A
</ins><dfn title="list" id="dfn-list"><ins class="diff-chg">
list
</ins></dfn><ins class="diff-chg">
is
an
ordered
sequence
of
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a>,<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
nodes
</ins></a>,<ins class="diff-chg">
and
</ins><a class="tref internalDFN" title="json-ld_value" href="#dfn-json-ld_value"><ins class="diff-chg">
JSON-LD
values
</ins></a>.</li></ul><div class="issue"><div class="issue-title"><span><ins class="diff-chg">
Issue
</ins></span></div><p class=""><ins class="diff-chg">
In
contrast
to
the
RDF
data
model
</ins>
as
<del class="diff-old">described
</del>
<ins class="diff-chg">defined
</ins>
in
[
<cite>
<del class="diff-old">RFC4627
</del>
<a class="bibref" href="#bib-RDF-CONCEPTS">
<ins class="diff-chg">RDF-CONCEPTS
</ins>
</a>
</cite>
<del class="diff-old">].
</del>
<ins class="diff-chg">],
JSON-LD
allows
blank
nodes
as
property
labels
and
graph
names.
This
feature
is
controversial
in
the
RDF
WG
and
may
be
removed
in
the
future.
</ins>
</p>
</div>
<p>
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
<del class="diff-old">introduces
a
number
of
keywords
of
the
form
'
@
'
followed
</del>
<ins class="diff-chg">documents
</ins></a><em class="rfc2119" title="may"><ins class="diff-chg">
may
</ins></em><ins class="diff-chg">
contain
data
that
cannot
be
represented
</ins>
by
<ins class="diff-new">the
</ins><a class="tref internalDFN" title="json-ld_data_model" href="#dfn-json-ld_data_model"><ins class="diff-new">
data
model
</ins></a><ins class="diff-new">
defined
above.
Unless
otherwise
specified,
such
data
is
ignored
when
</ins>
a
<del class="diff-old">set
of
one
or
more
lower
case
alphabetic
characters
(
@[a-z]+
).
</del>
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
<del class="diff-old">documents
should
</del>
<ins class="diff-chg">document
</ins></a><ins class="diff-chg">
is
being
processed.
This
means,
e.g.,
that
properties
which
are
</ins>
not
<del class="diff-old">define
terms
beginning
with
'
@
'.
(See
</del>
<ins class="diff-chg">mapped
to
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a><ins class="diff-chg">
or
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
node
</ins></a><ins class="diff-chg">
will
be
ignored.
</ins></p><p style="text-align: center"><img src="linked-data-graph.png" title="An illustration of JSON-LD's data model" /></p><p style="text-align: center"><ins class="diff-chg">
Figure
1:
An
illustration
of
JSON-LD's
data
model.
</ins></p></section><section class="appendix normative" id="json-ld-grammar"><h2>
<span class="secno">
<del class="diff-old">3.4
</del>
<ins class="diff-chg">B.
</ins>
</span>
<del class="diff-old">Syntax
Tokens
and
Keywords
</del>
<ins class="diff-chg">JSON-LD
Grammar
</ins></h2><em><ins class="diff-chg">
This
section
is
normative
</ins></em><div class="issue"><div class="issue-title"><a href="https://github.com/json-ld/json-ld.org/issues/114"><span><ins class="diff-chg">
Issue
114
</ins>
</span>
</a>
<del class="diff-old">for
</del>
</div>
<p class="">
<ins class="diff-chg">This
section
is
an
attempt
to
formalize
</ins>
a
<del class="diff-old">complete
definition
of
JSON-LD
keywords).
</del>
<ins class="diff-chg">normative
grammar
for
JSON-LD.
</ins></p></div><p><ins class="diff-chg">
This
appendix
restates
the
syntactic
conventions
described
in
the
previous
sections
more
formally.
</ins>
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
The
JSON-LD
context
allows
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keywords
</a>
<del class="diff-old">to
be
aliased
within
the
active
context
.
</del>
<a href="#aliasing-keywords" class="sec-ref">
<span class="secno">
<ins class="diff-chg">6.13
</ins></span><span class="sec-title"><ins class="diff-chg">
Aliasing
Keywords
</ins></span></a><ins class="diff-chg">
).
</ins>
Whenever
a
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
is
<del class="diff-old">discussed,
</del>
<ins class="diff-chg">discussed
in
</ins>
this
<del class="diff-old">is
</del>
<ins class="diff-chg">grammar,
the
statements
</ins>
also
<del class="diff-old">understood
to
</del>
apply
to
an
alias
for
that
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>.
For
example,
if
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>
defines
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
<code>
id
</code>
as
an
alias
for
<code>
@id
</code>,
that
alias
may
be
legitimately
used
as
a
substitution
for
<code>
@id
</code>.
Note
that
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
aliases
are
not
expanded
during
context
processing.
</p>
</div>
<p>
A
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
document
<del class="diff-old">is
either
</del>
</a>
<em class="rfc2119" title="must">
<ins class="diff-chg">must
</ins></em><ins class="diff-chg">
be
</ins>
a
<ins class="diff-new">valid
JSON
document
as
described
in
[
</ins><cite><a class="bibref" href="#bib-RFC4627"><ins class="diff-new">
RFC4627
</ins></a></cite><ins class="diff-new">
].
</ins></p><p><ins class="diff-new">
A
</ins><a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document"><ins class="diff-new">
JSON-LD
document
</ins></a><em class="rfc2119" title="must"><ins class="diff-new">
must
</ins></em><ins class="diff-new">
be
</ins>
a
single
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
or
a
JSON
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
containing
a
set
of
one
or
more
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definitions
</del>
<ins class="diff-chg">objects
</ins>
</a>.
</p>
<del class="diff-old">{
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
[
  {
    &quot;name&quot;: &quot;Manu Sporny&quot;,
    &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
    &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
  }, {
    &quot;name&quot;: &quot;Gregg Kellogg&quot;,
    &quot;homepage&quot;: &quot;http://greggkellogg.net/&quot;,
    &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/gkellogg&quot;
  }
]
</del>
<section id="grammar-node-object" typeof="bibo:Chapter" resource="#grammar-node-object" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">A.1
</del>
<ins class="diff-chg">B.1
</ins>
</span>
Node
<del class="diff-old">Definition
</del>
<ins class="diff-chg">Object
</ins>
</h3>
<p>
A
<dfn title="node_object" id="dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins></dfn><ins class="diff-chg">
represents
zero
or
more
properties
of
a
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
node
</ins></a><ins class="diff-chg">
in
the
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-chg">
JSON-LD
graph
</ins></a><ins class="diff-chg">
serialized
by
the
</ins><a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document"><ins class="diff-chg">
JSON-LD
document
</ins></a>.<ins class="diff-chg">
A
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-chg">
JSON
Object
</ins>
</a>
is
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
<ins class="diff-new">node
object
</ins></a><ins class="diff-new">
if
it
exists
outside
of
the
JSON-LD
Context
and:
</ins></p><ul><li><ins class="diff-new">
it
does
not
contain
the
</ins><code><ins class="diff-new">
@value
</ins></code>,<code><ins class="diff-new">
@list
</ins></code>,<code><ins class="diff-new">
@annotation
</ins></code>,<ins class="diff-new">
or
</ins><code><ins class="diff-new">
@set
</ins></code><ins class="diff-new">
keywords,
or
</ins></li><li><ins class="diff-new">
it
does
not
contain
the
</ins><code><ins class="diff-new">
@graph
</ins></code><ins class="diff-new">
keyword
and
is
the
top-most
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-new">
JSON
Object
</ins></a><ins class="diff-new">
in
the
JSON-LD
document.
</ins></li></ul><ins class="diff-new">
The
properties
of
a
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-new">
node
</ins></a><ins class="diff-new">
in
the
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-new">
JSON-LD
graph
</ins></a><ins class="diff-new">
may
be
spread
among
different
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
objects
</ins></a><ins class="diff-new">
within
a
document.
When
that
happens,
the
keys
of
the
different
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
objects
</ins></a><ins class="diff-new">
are
merged
to
create
the
properties
of
the
resulting
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-new">
node
</ins></a>.<p></p><p><ins class="diff-new">
A
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a><em class="rfc2119" title="must"><ins class="diff-new">
must
</ins></em><ins class="diff-new">
be
a
</ins>
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
<del class="diff-old">containing
</del>
<ins class="diff-chg">that
contains
</ins>
one
or
more
key-value
pairs.
Keys
<del class="diff-old">are
</del>
<em class="rfc2119" title="must">
<ins class="diff-chg">must
</ins></em><ins class="diff-chg">
either
be
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
s,
</del>
<ins class="diff-chg">IRIs
</ins></a>,
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<del class="diff-old">IRI
s,
</del>
<ins class="diff-chg">IRIs
</ins></a>,
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">terms
</ins>
</a>
<del class="diff-old">s
defined
within
</del>
<ins class="diff-chg">valid
in
</ins>
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>,
or
one
of
the
following
<del class="diff-old">keywords:
</del>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
<ins class="diff-chg">keywords
</ins></a>:
</p>
<ul>
<li>
<code>
@context
</code>,
</li>
<li>
<code>
@graph
</code>,
</li>
<li>
<code>
@id
</code>,
or
</li>
<li>
<code>
@type
</code>
</li>
</ul>
<p>
If
the
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
contains
the
<code>
@context
</code>
key,
its
value
<em class="rfc2119" title="must">
must
</em>
be
one
of
the
following:
</p>
<ul>
<li>
<del class="diff-old">a
string
with
the
lexical
form
of
</del>
<ins class="diff-chg">an
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
</li>
<li>
a
<del class="diff-old">JSON
object
conforming
the
the
syntax
requirements
stated
in
A.6
Context
Definition
</del>
<a class="tref internalDFN" title="context_definition" href="#dfn-context_definition">
<ins class="diff-chg">context
definition
</ins>
</a>,
or
</li>
<li>
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
composed
of
any
number
of
the
previous
two
expressions.
</li>
</ul>
<del class="diff-old">{
  ,
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
See
3.8
Node
Identifiers
,
4.1
Compact
IRIs
,
and
4.12
Identifying
Unlabeled
Nodes
for
further
discussion
on
@id
values.
</del>
<p>
If
the
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
contains
the
<code>
@id
</code>
key,
<del class="diff-old">it's
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">a
string
having
the
lexical
form
of
</del>
<ins class="diff-chg">an
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
<ins class="diff-new">a
</ins>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
(including
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier">
<ins class="diff-chg">blank
</ins>
node
<ins class="diff-new">identifiers
</ins>
</a>
),
or
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
defined
in
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>
expanding
into
an
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
or
<del class="diff-old">an
unlabeled
</del>
<ins class="diff-chg">a
</ins><a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier"><ins class="diff-chg">
blank
</ins>
node
<ins class="diff-new">identifier
</ins>
</a>.
<del class="diff-old">{
  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,
  ,
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</del>
<ins class="diff-chg">See
</ins><a href="#node-identifiers" class="sec-ref">
<span class="secno">
<ins class="diff-chg">5.4
</ins></span><span class="sec-title"><ins class="diff-chg">
Node
Identifiers
</ins></span></a>,<a href="#compact-iris" class="sec-ref"><span class="secno"><ins class="diff-chg">
6.1
</ins></span><span class="sec-title"><ins class="diff-chg">
Compact
IRIs
</ins></span></a>,<ins class="diff-chg">
and
</ins><a href="#identifying-blank-nodes" class="sec-ref"><span class="secno"><ins class="diff-chg">
6.12
</ins></span><span class="sec-title"><ins class="diff-chg">
Identifying
Blank
Nodes
</ins></span></a><ins class="diff-chg">
for
further
discussion
on
</ins><code><ins class="diff-chg">
@id
</ins></code><ins class="diff-chg">
values.
</ins></p>
<p>
If
the
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
contains
the
<code>
@type
</code>
key,
<del class="diff-old">it's
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
be
either
<del class="diff-old">a
string
having
the
lexical
form
of
</del>
<ins class="diff-chg">an
</ins>
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
<ins class="diff-new">a
</ins>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
<del class="diff-old">,
</del>
</a>
<ins class="diff-chg">(excluding
</ins><a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier"><ins class="diff-chg">
blank
node
identifier
</ins></a><ins class="diff-chg">
),
</ins>
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
defined
in
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>
expanding
into
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
or
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
of
any
of
these.
<del class="diff-old">A
JSON-LD
processor
should
process
non-conforming
documents
having
@type
values
including
node
definition
or
node
reference
entries
but
must
discard
everything
except
for
the
value
of
the
@id
key.
{
  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,
  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
  ,
  &quot;name&quot;: &quot;Manu Sporny&quot;,
  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
}
</del>
See
<a href="#specifying-the-type" class="sec-ref">
<span class="secno">
<del class="diff-old">3.9
</del>
<ins class="diff-chg">5.5
</ins>
</span>
<span class="sec-title">
Specifying
the
Type
</span>
</a>
for
further
discussion
on
<code>
@type
</code>
values.
</p>
<p>
If
the
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
contains
the
<code>
@graph
</code>
key,
<del class="diff-old">it's
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
be
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
or
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
of
zero
or
more
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definitions
</del>
<ins class="diff-chg">objects
</ins>
</a>.
If
the
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
contains
an
<code>
@id
</code>
keyword,
its
value
is
used
as
the
label
of
a
named
graph.
<ins class="diff-new">See
</ins><a href="#named-graphs" class="sec-ref"><span class="secno"><ins class="diff-new">
6.11
</ins></span><span class="sec-title"><ins class="diff-new">
Named
Graphs
</ins></span></a><ins class="diff-new">
for
further
discussion
on
</ins><code><ins class="diff-new">
@graph
</ins></code><ins class="diff-new">
values.
</ins>
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
As
a
special
case,
if
<del class="diff-old">the
</del>
<ins class="diff-chg">a
</ins>
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
contains
no
keys
other
than
<code>
@graph
</code>
and
<code>
@context
</code>,
and
the
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
is
the
root
of
the
JSON-LD
document,
the
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
is
not
treated
as
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
;
this
is
used
as
a
way
of
defining
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
definitions
</a>
that
may
not
form
a
connected
graph.
This
allows
a
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
to
be
defined
which
is
shared
by
all
of
the
constituent
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definitions
</del>
<ins class="diff-chg">objects
</ins>
</a>.
</p>
</div>
<del class="diff-old">{
  &quot;@context&quot;: ...,
  &quot;&quot;:
  [
    {
      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;name&quot;: &quot;Manu Sporny&quot;,
      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
    },
    {
      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
    }
  ]
}
See
4.11
Named
Graphs
for
further
discussion
on
@graph
values.
</del>
<p>
A
<a class="tref internalDFN" title="json-ld_document" href="#dfn-json-ld_document">
JSON-LD
document
</a>
<em class="rfc2119" title="must not">
must
not
</em>
contain
any
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>
<del class="diff-old">or
alias
</del>
that
expands
to
another
keyword.
</p>
<p>
<del class="diff-old">Other
keys
</del>
<ins class="diff-chg">Keys
in
a
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-chg">
node
object
</ins></a><ins class="diff-chg">
that
are
not
</ins><a class="tref internalDFN" title="keyword" href="#dfn-keyword"><ins class="diff-chg">
keywords
</ins></a>
<em class="rfc2119" title="must">
must
</em>
expand
to
an
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
using
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>.
The
values
associated
with
these
keys
<del class="diff-old">may
</del>
<em class="rfc2119" title="must">
<ins class="diff-chg">must
</ins></em>
be
<del class="diff-old">any
</del>
<ins class="diff-chg">one
</ins>
of
the
following:
</p>
<ul>
<li>
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
</li>
<li>
<a class="tref internalDFN" title="number" href="#dfn-number">
number
</a>,
</li>
<li>
<a class="tref internalDFN" title="true" href="#dfn-true">
true
</a>,
</li>
<li>
<a class="tref internalDFN" title="false" href="#dfn-false">
false
</a>,
</li>
<li>
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>,
</li>
<li>
<del class="diff-old">node
reference
,
</del>
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>,
</li>
<li>
<a class="tref internalDFN" title="expanded_typed_value" href="#dfn-expanded_typed_value">
<ins class="diff-chg">expanded
</ins>
typed
value
</a>,
</li>
<li>
<a class="tref internalDFN" title="expanded_language-tagged_string" href="#dfn-expanded_language-tagged_string">
<ins class="diff-chg">expanded
</ins>
language-tagged
string
</a>,
</li>
<li>
<del class="diff-old">@set
or
@list
definition
(see
4.9
Sets
and
Lists
</del>
<a class="tref internalDFN" title="list" href="#dfn-list">
<ins class="diff-chg">list
</ins>
</a>
<del class="diff-old">),
</del>
<ins class="diff-chg">or
</ins><a class="tref internalDFN" title="set" href="#dfn-set"><ins class="diff-chg">
set
</ins></a>,
</li>
<li>
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
<ins class="diff-new">of
</ins>
zero
or
more
of
<del class="diff-old">these,
or
</del>
<ins class="diff-chg">the
possibilities
above,
</ins>
</li>
<li>
a
<a class="tref internalDFN" title="language_map" href="#dfn-language_map">
language
map
</a>,
<ins class="diff-new">or
</ins></li><li><ins class="diff-new">
an
</ins><a class="tref internalDFN" title="annotation_map" href="#dfn-annotation_map"><ins class="diff-new">
annotation
map
</ins>
</a>
</li>
</ul>
</section>
<section id="grammar-term-reference" typeof="bibo:Chapter" resource="#grammar-term-reference" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">A.2
</del>
<ins class="diff-chg">B.2
</ins>
</span>
<del class="diff-old">Node
Reference
</del>
<ins class="diff-chg">Term
</ins>
</h3>
<p>
A
<del class="diff-old">JSON
object
</del>
<dfn title="term" id="dfn-term">
<ins class="diff-chg">term
</ins></dfn><ins class="diff-chg">
is
a
short-hand
</ins><a class="tref internalDFN" title="string" href="#dfn-string"><ins class="diff-chg">
string
</ins>
</a>
<del class="diff-old">containing
only
</del>
<ins class="diff-chg">that
expands
to
an
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier"><ins class="diff-chg">
IRI
</ins></abbr></a><ins class="diff-chg">
or
a
</ins><a class="tref internalDFN" title="blank_node_identifier" href="#dfn-blank_node_identifier"><ins class="diff-chg">
blank
node
identifier
</ins></a>.</p><p><ins class="diff-chg">
A
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
term
</ins></a><em class="rfc2119" title="must not"><ins class="diff-chg">
must
not
</ins></em><ins class="diff-chg">
equal
any
of
</ins>
the
<ins class="diff-new">JSON-LD
</ins><a class="tref internalDFN" title="keyword" href="#dfn-keyword"><ins class="diff-new">
keywords
</ins></a>.</p><p><ins class="diff-new">
To
avoid
forward-compatibility
issues,
a
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><em class="rfc2119" title="should not"><ins class="diff-new">
should
not
</ins></em><ins class="diff-new">
start
with
an
</ins>
<code>
<del class="diff-old">@id
</del>
<ins class="diff-chg">@
</ins>
</code>
<del class="diff-old">(or
an
alias
for
</del>
<ins class="diff-chg">character
as
future
versions
of
JSON-LD
may
introduce
additional
</ins><a class="tref internalDFN" title="keyword" href="#dfn-keyword"><ins class="diff-chg">
keywords
</ins></a>.<ins class="diff-chg">
Furthermore,
the
use
of
empty
terms
(
</ins>
<code>
<del class="diff-old">@id
</del>
<ins class="diff-chg">&quot;&quot;
</ins>
</code>
)
is
<del class="diff-old">a
node
reference
</del>
<ins class="diff-chg">discouraged
as
not
all
programming
languages
are
able
to
handle
empty
property
names.
</ins></p><p><ins class="diff-chg">
See
</ins><a href="#the-context" class="sec-ref"><span class="secno"><ins class="diff-chg">
5.1
</ins></span><span class="sec-title"><ins class="diff-chg">
The
Context
</ins></span>
</a>
and
<del class="diff-old">not
a
node
definition
</del>
<a href="#iris" class="sec-ref">
<span class="secno">
<ins class="diff-chg">5.3
</ins></span><span class="sec-title"><ins class="diff-chg">
IRIs
</ins></span></a><ins class="diff-chg">
for
further
discussion
on
mapping
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
terms
</ins></a><ins class="diff-chg">
to
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins>
</a>.
</p>
<del class="diff-old">{
  &quot;@context&quot;: ...,
  &quot;@graph&quot;: [
    {
      &quot;@id&quot;: &quot;http://example.org/library&quot;,
      &quot;@type&quot;: &quot;ex:Library&quot;,
      
    }, {
      &quot;@id&quot;: &quot;http://example.org/library/the-republic&quot;,
      &quot;@type&quot;: &quot;ex:Book&quot;,
      &quot;dc:creator&quot;: &quot;Plato&quot;,
      &quot;dc:title&quot;: &quot;The Republic&quot;,
      
    }, {
      &quot;@id&quot;: &quot;http://example.org/library/the-republic#introduction&quot;,
      &quot;@type&quot;: &quot;ex:Chapter&quot;,
      &quot;dc:description&quot;: &quot;An introductory chapter on The Republic.&quot;,
      &quot;dc:title&quot;: &quot;The Introduction&quot;
    }
  ]
}
}
</del>
</section>
<section id="grammar-language-map" typeof="bibo:Chapter" resource="#grammar-language-map" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">A.3
</del>
<ins class="diff-chg">B.3
</ins>
</span>
Language
Map
</h3>
<p>
A
<dfn title="language_map" id="dfn-language_map">
<ins class="diff-new">language
map
</ins></dfn><ins class="diff-new">
is
used
to
associate
a
language
with
a
value
in
a
way
that
allows
easy
programmatic
access.
A
</ins>
<a class="tref internalDFN" title="language_map" href="#dfn-language_map">
language
map
</a>
may
be
used
as
a
term
value
within
a
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>
if
the
term
is
defined
with
<code>
@container
</code>
set
to
<code>
@language
</code>.
The
keys
of
a
<a class="tref internalDFN" title="language_map" href="#dfn-language_map">
language
map
</a>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">a
</del>
<ins class="diff-chg">lowercase
</ins>
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
]
<a class="tref internalDFN" title="string" href="#dfn-string">
<ins class="diff-new">strings
</ins></a><ins class="diff-new">
with
an
associated
value
that
is
any
of
the
following
types:
</ins></p><ul><li><a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
<ins class="diff-new">or
</ins></li><li><ins class="diff-new">
an
</ins><a class="tref internalDFN" title="array" href="#dfn-array"><ins class="diff-new">
array
</ins></a><ins class="diff-new">
of
zero
or
more
strings
</ins></li></ul><p><ins class="diff-new">
See
</ins><a href="#language-tagged-strings" class="sec-ref"><span class="secno"><ins class="diff-new">
6.3
</ins></span><span class="sec-title"><ins class="diff-new">
Language-tagged
Strings
</ins></span></a><ins class="diff-new">
for
further
discussion
on
language
maps.
</ins></p></section><section id="grammar-annotation-map" typeof="bibo:Chapter" resource="#grammar-annotation-map" rel="bibo:chapter"><h3><span class="secno"><ins class="diff-new">
B.4
</ins></span><ins class="diff-new">
Annotation
Map
</ins></h3><p><ins class="diff-new">
An
</ins><dfn title="annotation_map" id="dfn-annotation_map"><ins class="diff-new">
annotation
map
</ins></dfn><ins class="diff-new">
allows
keys
that
have
no
semantic
meaning,
but
should
be
preserved
regardless,
to
be
used
in
JSON-LD
documents.
An
</ins><a class="tref internalDFN" title="annotation_map" href="#dfn-annotation_map"><ins class="diff-new">
annotation
map
</ins></a><ins class="diff-new">
may
be
used
as
a
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><ins class="diff-new">
value
within
a
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a><ins class="diff-new">
if
the
term
is
defined
with
</ins><code><ins class="diff-new">
@container
</ins></code><ins class="diff-new">
set
to
</ins><code><ins class="diff-new">
@annotation
</ins></code>.<ins class="diff-new">
The
keys
of
a
</ins><a class="tref internalDFN" title="annotation_map" href="#dfn-annotation_map"><ins class="diff-new">
annotation
map
</ins></a><em class="rfc2119" title="must"><ins class="diff-new">
must
</ins></em><ins class="diff-new">
be
</ins><a class="tref internalDFN" title="string" href="#dfn-string"><ins class="diff-new">
strings
</ins></a>
with
an
associated
value
that
is
any
of
the
following
types:
</p>
<ul>
<li>
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
</li>
<li>
<a class="tref internalDFN" title="number" href="#dfn-number">
number
</a>,
</li>
<li>
<a class="tref internalDFN" title="true" href="#dfn-true">
true
</a>,
</li>
<li>
<a class="tref internalDFN" title="false" href="#dfn-false">
false
</a>,
</li>
<li>
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>,
</li>
<li>
<del class="diff-old">node
reference
,
</del>
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
node
<del class="diff-old">definition
</del>
<ins class="diff-chg">object
</ins>
</a>,
</li>
<li>
<del class="diff-old">typed
</del>
<a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value">
<ins class="diff-chg">expanded
</ins>
value
</a>,
</li>
<li>
<del class="diff-old">language-tagged
string
,
@set
or
@list
definition
(see
4.9
Sets
and
Lists
),
or
</del>
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
<ins class="diff-new">of
</ins>
zero
or
more
of
<del class="diff-old">these
</del>
<ins class="diff-chg">the
above
possibilities
</ins>
</li>
</ul>
<del class="diff-old">We
had
also
discussed
values
other
than
strings,
such
as
those
that
might
represent
a
more
reified
version
of
a
value
with
other
properties,
such
as
is
described
using
SKOS-XL
.
{
  &quot;@context&quot;:
  {
    &quot;title&quot;:
    {
      &quot;@id&quot;: &quot;http://purl.org/dc/terms/title&quot;
      
    }
  },
...
  &quot;title&quot;:
  {
    &quot;en&quot;: &quot;JSON-LD Syntax&quot;,
    &quot;ru&quot;: &quot;JSON-LD Синтаксис&quot;,
    &quot;ja&quot;: &quot;JSON-LDの構文&quot;
  }
...
}
</del>
<p>
<ins class="diff-chg">See
</ins><a href="#data-annotations" class="sec-ref">
<span class="secno">
<ins class="diff-chg">6.14
</ins></span><span class="sec-title"><ins class="diff-chg">
Data
Annotations
</ins></span></a><ins class="diff-chg">
for
further
information
on
this
topic.
</ins></p>
</section>
<section id="grammar-expanded-values" typeof="bibo:Chapter" resource="#grammar-expanded-values" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">A.4
</del>
<ins class="diff-chg">B.5
</ins>
</span>
Expanded
Values
</h3>
<p>
An
<dfn title="expanded_value" id="dfn-expanded_value">
expanded
value
</dfn>
is
<ins class="diff-new">used
to
explicitly
associate
a
type
or
a
language
with
a
value
to
create
a
</ins><a class="tref internalDFN" title="typed_value" href="#dfn-typed_value"><ins class="diff-new">
typed
value
</ins></a><ins class="diff-new">
or
a
</ins><a class="tref internalDFN" title="language-tagged_string" href="#dfn-language-tagged_string"><ins class="diff-new">
language-tagged
string
</ins></a>.</p><p><ins class="diff-new">
An
</ins><a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value"><ins class="diff-new">
expanded
value
</ins></a><em class="rfc2119" title="must"><ins class="diff-new">
must
</ins></em><ins class="diff-new">
be
</ins>
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
containing
the
<code>
@value
</code>
<del class="diff-old">key,
or
an
alias
for
the
@value
value
</del>
key.
It
<em class="rfc2119" title="may">
may
</em>
also
contain
<del class="diff-old">the
</del>
<ins class="diff-chg">a
</ins>
<code>
@type
</code>
or
<ins class="diff-new">a
</ins>
<code>
@language
</code>
<del class="diff-old">keys,
or
their
respective
keyword
aliases.
</del>
<ins class="diff-chg">key
but
</ins><em class="rfc2119" title="must not"><ins class="diff-chg">
must
not
</ins></em><ins class="diff-chg">
contain
both
a
</ins><code><ins class="diff-chg">
@type
</ins></code><ins class="diff-chg">
and
a
</ins><code><ins class="diff-chg">
@language
</ins></code><ins class="diff-chg">
key.
</ins>
An
<a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value">
expanded
value
</a>
<em class="rfc2119" title="must not">
must
not
</em>
contain
keys
other
than
<code>
@value
</code>,
<code>
@language
</code>,
and
<code>
@type
</code>.
An
<a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value">
expanded
value
</a>
<del class="diff-old">must
not
contain
both
the
</del>
<ins class="diff-chg">that
contains
a
</ins>
<code>
<del class="diff-old">@language
</del>
<ins class="diff-chg">@type
</ins>
</code>
<del class="diff-old">and
</del>
<ins class="diff-chg">key
is
called
an
</ins><dfn title="expanded_typed_value" id="dfn-expanded_typed_value"><ins class="diff-chg">
expanded
typed
value
</ins></dfn>.<ins class="diff-chg">
An
</ins><a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value"><ins class="diff-chg">
expanded
value
</ins></a><ins class="diff-chg">
that
contains
a
</ins>
<code>
<del class="diff-old">@type
</del>
<ins class="diff-chg">@language
</ins>
</code>
<del class="diff-old">keys.
</del>
<ins class="diff-chg">key
is
called
an
</ins><dfn title="expanded_language-tagged_string" id="dfn-expanded_language-tagged_string"><ins class="diff-chg">
expanded
language-tagged
string
</ins></dfn>.
</p>
<p>
The
value
<del class="diff-old">of
</del>
<ins class="diff-chg">associated
with
</ins>
the
<code>
@value
</code>
<del class="diff-old">key,
or
its
alias,
</del>
<ins class="diff-chg">key
</ins>
<em class="rfc2119" title="must">
must
</em>
be
either
a
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
<a class="tref internalDFN" title="number" href="#dfn-number">
number
</a>,
<a class="tref internalDFN" title="true" href="#dfn-true">
true
</a>,
<del class="diff-old">or
</del>
<a class="tref internalDFN" title="false" href="#dfn-false">
false
</a>
<ins class="diff-new">or
</ins><a class="tref internalDFN" title="null" href="#dfn-null"><ins class="diff-new">
null
</ins>
</a>.
</p>
<p>
<del class="diff-old">If
an
expanded
value
contains
a
@language
key,
it
must
not
contain
any
other
key
except
@value
.
</del>
The
value
<del class="diff-old">of
</del>
<ins class="diff-chg">associated
with
</ins>
the
<code>
@language
</code>
key
<em class="rfc2119" title="must">
must
</em>
have
the
lexical
form
described
in
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
],
or
be
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>.
</p>
<p>
<del class="diff-old">If
an
expanded
</del>
<ins class="diff-chg">The
</ins>
value
<del class="diff-old">contains
a
</del>
<ins class="diff-chg">associated
with
the
</ins>
<code>
<del class="diff-old">@type
</del>
<ins class="diff-chg">@annotation
</ins>
</code>
<del class="diff-old">key,
it
</del>
<ins class="diff-chg">key
</ins><em class="rfc2119" title="must">
must
<del class="diff-old">not
</del>
</em>
<del class="diff-old">contain
any
other
key
except
@value
.
</del>
<ins class="diff-chg">be
a
</ins><a class="tref internalDFN" title="string" href="#dfn-string"><ins class="diff-chg">
string
</ins></a>.</p><p>
The
value
<del class="diff-old">of
</del>
<ins class="diff-chg">associated
with
the
</ins>
<code>
@type
</code>
<ins class="diff-new">key
</ins>
<em class="rfc2119" title="must">
must
</em>
be
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>,
<ins class="diff-new">a
</ins>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
<ins class="diff-new">an
</ins>
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
or
<code>
null
</code>.
</p>
<p>
See
<a href="#typed-values" class="sec-ref">
<span class="secno">
<del class="diff-old">4.2
</del>
<ins class="diff-chg">6.2
</ins>
</span>
<span class="sec-title">
Typed
Values
</span>
</a>
and
<a href="#language-tagged-strings" class="sec-ref">
<span class="secno">
<del class="diff-old">4.3
</del>
<ins class="diff-chg">6.3
</ins>
</span>
<span class="sec-title">
Language-tagged
Strings
</span>
</a>
for
<del class="diff-old">a
further
discussion
of
</del>
<ins class="diff-chg">more
information
on
</ins>
<a class="tref internalDFN" title="expanded_value" href="#dfn-expanded_value">
expanded
values
</a>.
</p>
</section>
<section id="grammar-set-list" typeof="bibo:Chapter" resource="#grammar-set-list" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">A.5
</del>
<ins class="diff-chg">B.6
</ins>
</span>
List
and
Set
Values
</h3>
<p>
A
<a class="tref internalDFN" title="list" href="#dfn-list">
list
</a>
<ins class="diff-new">represents
an
</ins><em><ins class="diff-new">
ordered
</ins></em><ins class="diff-new">
set
of
values.
A
</ins><dfn title="set" id="dfn-set"><ins class="diff-new">
set
</ins>
</dfn>
<del class="diff-old">is
</del>
<ins class="diff-chg">represents
an
</ins><em><ins class="diff-chg">
unordered
</ins></em><ins class="diff-chg">
set
of
values.
Unless
otherwise
specified
(typically
through
the
use
of
</ins>
a
<del class="diff-old">JSON
object
</del>
<a class="tref internalDFN" title="list" href="#dfn-list">
<ins class="diff-chg">list
</ins>
</a>
<del class="diff-old">having
only
</del>
<ins class="diff-chg">),
</ins><a class="tref internalDFN" title="array" href="#dfn-array"><ins class="diff-chg">
arrays
</ins></a><ins class="diff-chg">
are
unordered
in
JSON-LD.
As
such,
the
</ins><code><ins class="diff-chg">
@set
</ins></code><ins class="diff-chg">
keyword,
when
used
in
the
body
of
a
JSON-LD
document,
represents
just
syntactic
sugar
which
is
optimized
away
when
processing
the
document.
However,
it
is
very
helpful
when
used
within
</ins>
the
<ins class="diff-new">context
of
a
document.
Values
of
terms
associated
with
a
</ins><code><ins class="diff-new">
@set
</ins></code><ins class="diff-new">
or
</ins>
<code>
@list
</code>
<del class="diff-old">keyword
.
Its
</del>
<ins class="diff-chg">container
will
always
be
represented
in
the
form
of
an
array
when
a
document
is
processed
-
even
if
there
is
just
a
single
</ins>
value
<ins class="diff-new">that
would
otherwise
be
optimized
to
a
non-array
form
in
</ins><a href="#compact-document-form"><ins class="diff-new">
compact
document
form
</ins></a>.<ins class="diff-new">
This
simplifies
post-processing
of
the
data
as
the
data
is
always
in
array
form.
</ins></p><p><ins class="diff-new">
A
</ins><a class="tref internalDFN" title="list" href="#dfn-list"><ins class="diff-new">
list
</ins></a>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">an
array
</del>
<ins class="diff-chg">a
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-chg">
JSON
object
</ins>
</a>
<del class="diff-old">of
any
of
</del>
<ins class="diff-chg">that
contains
a
single
key-value
pair
where
</ins>
the
<del class="diff-old">following:
</del>
<ins class="diff-chg">key
is
</ins><code><ins class="diff-chg">
@list
</ins></code>.
</p>
<del class="diff-old">string
,
node
reference
,
node
definition
,
typed
value
,
or
language-tagged
string
.
</del>
<p>
A
<a class="tref internalDFN" title="set" href="#dfn-set">
set
<del class="diff-old">is
</del>
</a>
<em class="rfc2119" title="must">
<ins class="diff-chg">must
</ins></em><ins class="diff-chg">
be
</ins>
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
<del class="diff-old">having
only
</del>
<ins class="diff-chg">that
contains
a
single
key-value
pair
where
</ins>
the
<ins class="diff-new">key
is
</ins>
<code>
@set
<del class="diff-old">keyword
.
Its
</del>
</code>.
</p>
<p>
<ins class="diff-chg">In
both
cases,
the
</ins>
value
<ins class="diff-new">associated
with
the
key
</ins>
<em class="rfc2119" title="must">
must
</em>
be
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
of
any
of
the
following:
</p>
<ul>
<li>
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
</li>
<li>
<del class="diff-old">node
reference
</del>
<a class="tref internalDFN" title="number" href="#dfn-number">
<ins class="diff-chg">number
</ins>
</a>,
</li>
<li>
<del class="diff-old">node
definition
</del>
<a class="tref internalDFN" title="true" href="#dfn-true">
<ins class="diff-chg">true
</ins>
</a>,
</li>
<li>
<del class="diff-old">typed
value
</del>
<a class="tref internalDFN" title="false" href="#dfn-false">
<ins class="diff-chg">false
</ins>
</a>,
</li>
<li>
<del class="diff-old">language-tagged
string
</del>
<a class="tref internalDFN" title="null" href="#dfn-null">
<ins class="diff-chg">null
</ins>
</a>,
</li>
<li>
<del class="diff-old">@set
or
@list
definition
(see
4.9
Sets
and
Lists
</del>
<a class="tref internalDFN" title="node_object" href="#dfn-node_object">
<ins class="diff-chg">node
object
</ins></a>,</li><li>
<del class="diff-old">),
</del>
<a class="tref internalDFN" title="expanded_typed_value" href="#dfn-expanded_typed_value">
<ins class="diff-chg">expanded
typed
value
</ins></a>,
or
</li>
<li>
<del class="diff-old">an
array
</del>
<a class="tref internalDFN" title="expanded_language-tagged_string" href="#dfn-expanded_language-tagged_string">
<ins class="diff-chg">expanded
language-tagged
string
</ins>
</a>
<del class="diff-old">zero
or
more
of
these.
</del>
</li>
</ul>
<p>
See
<a href="#sets-and-lists" class="sec-ref">
<span class="secno">
<del class="diff-old">4.9
</del>
<ins class="diff-chg">6.9
</ins>
</span>
<span class="sec-title">
Sets
and
Lists
</span>
</a>
for
<del class="diff-old">a
</del>
further
discussion
<del class="diff-old">of
</del>
<ins class="diff-chg">on
</ins>
List
and
Set
Values.
</p>
</section>
<section id="grammar-context" typeof="bibo:Chapter" resource="#grammar-context" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">A.6
</del>
<ins class="diff-chg">B.7
</ins>
</span>
Context
Definition
</h3>
<p>
A
<dfn title="context_definition" id="dfn-context_definition">
context
definition
</dfn>
<del class="diff-old">is
</del>
<ins class="diff-chg">defines
a
</ins><a class="tref internalDFN" title="local_context" href="#dfn-local_context"><ins class="diff-chg">
local
context
</ins></a><ins class="diff-chg">
in
a
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-chg">
node
object
</ins></a>.</p><p><ins class="diff-chg">
A
</ins><a class="tref internalDFN" title="context_definition" href="#dfn-context_definition"><ins class="diff-chg">
context
definition
</ins></a><em class="rfc2119" title="must"><ins class="diff-chg">
must
</ins></em><ins class="diff-chg">
be
</ins>
a
<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
JSON
object
</a>
containing
one
or
more
key-value
pairs.
Keys
<del class="diff-old">are
non-keyword
strings
</del>
<em class="rfc2119" title="must">
<ins class="diff-chg">must
</ins></em><ins class="diff-chg">
either
be
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
terms
</ins>
</a>
or
<del class="diff-old">the
</del>
<code>
@language
</code>
or
<code>
@vocab
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keywords
</a>.
<del class="diff-old">A
context
definition
should
not
contain
any
keys
having
the
lexical
form
of
keyword
other
than
@language
or
@vocab
.
</del>
</p>
<p>
If
the
<a class="tref internalDFN" title="context_definition" href="#dfn-context_definition">
context
definition
</a>
has
a
<code>
@language
</code>
key,
<del class="diff-old">the
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
have
the
lexical
form
described
in
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
]
or
be
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>.
</p>
<p>
If
the
<a class="tref internalDFN" title="context_definition" href="#dfn-context_definition">
context
definition
</a>
has
a
<code>
@vocab
</code>
key,
<del class="diff-old">the
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
have
the
lexical
form
of
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>
or
be
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>.
</p>
<p>
<del class="diff-old">Other
keys
are
</del>
<a class="tref internalDFN" title="term" href="#dfn-term">
<del class="diff-old">term
</del>
<ins class="diff-chg">Term
</ins>
</a>
<del class="diff-old">definitions.
Their
</del>
values
<em class="rfc2119" title="must">
must
</em>
be
either
a
<a class="tref internalDFN" title="string" href="#dfn-string">
string
</a>,
<code>
<ins class="diff-new">null
</ins></code>,
or
<del class="diff-old">a
JSON
object
having
the
form
of
</del>
an
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
<del class="diff-old">(see
4.5
Expanded
Term
Definition
).
</del>
</a>.
</p>
<p>
An
<dfn title="expanded_term_definition" id="dfn-expanded_term_definition">
expanded
term
definition
</dfn>
is
<ins class="diff-new">used
to
describe
the
mapping
between
a
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><ins class="diff-new">
and
its
expanded
identifier,
as
well
as
other
properties
of
the
value
associated
with
the
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-new">
term
</ins></a><ins class="diff-new">
when
it
is
used
as
key
in
a
</ins><a class="tref internalDFN" title="node_object" href="#dfn-node_object"><ins class="diff-new">
node
object
</ins></a>.</p><p><ins class="diff-new">
An
</ins><a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition"><ins class="diff-new">
expanded
term
definition
</ins></a><em class="rfc2119" title="should"><ins class="diff-new">
should
</ins></em><ins class="diff-new">
be
a
</ins><a class="tref internalDFN" title="json_object" href="#dfn-json_object"><ins class="diff-new">
JSON
object
</ins></a>
composed
of
zero
or
more
keys
from
<code>
@id
</code>,
<code>
@type
</code>,
<code>
@language
</code>
or
<code>
@container
</code>.
An
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
</a>
<em class="rfc2119" title="should not">
should
not
</em>
contain
any
other
keys.
<del class="diff-old">All
values
associated
with
@id
must
expand
to
an
absolute
IRI
.
</del>
</p>
<p>
If
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
definition
is
not
<code>
<ins class="diff-new">null
</ins></code>,
a
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
or
<ins class="diff-new">an
</ins>
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
the
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
</a>
<em class="rfc2119" title="must">
must
</em>
include
the
<code>
@id
</code>
key.
</p>
<p>
If
the
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
</a>
contains
the
<code>
@id
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>,
<del class="diff-old">it
</del>
<ins class="diff-chg">its
value
</ins>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">a
string
having
the
lexical
form
of
</del>
<code>
<ins class="diff-chg">null
</ins></code>,<ins class="diff-chg">
an
</ins>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
<ins class="diff-new">a
</ins>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
defined
in
the
defining
<a class="tref internalDFN" title="context_definition" href="#dfn-context_definition">
context
definition
</a>
or
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>,
or
an
<a class="tref internalDFN" title="array" href="#dfn-array">
array
</a>
composed
of
any
of
the
previous
allowed
values.
</p>
<p>
If
the
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
</a>
contains
the
<code>
@type
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>,
<del class="diff-old">it
</del>
<ins class="diff-chg">its
value
</ins>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">a
string
having
the
lexical
form
of
</del>
<ins class="diff-chg">an
</ins>
<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
absolute
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
<ins class="diff-new">a
</ins>
<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
compact
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>,
<del class="diff-old">or
</del>
a
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
defined
in
the
defining
<a class="tref internalDFN" title="context_definition" href="#dfn-context_definition">
context
definition
</a>
or
the
<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
active
context
</a>,
<ins class="diff-new">or
the
</ins><code><ins class="diff-new">
@id
</ins></code><a class="tref internalDFN" title="keyword" href="#dfn-keyword"><ins class="diff-new">
keyword
</ins>
</a>.
</p>
<p>
If
the
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
</a>
contains
the
<code>
@language
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>,
<del class="diff-old">the
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
have
the
lexical
form
described
in
[
<cite>
<a class="bibref" href="#bib-BCP47">
BCP47
</a>
</cite>
]
or
be
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>.
</p>
<p>
If
the
<a class="tref internalDFN" title="expanded_term_definition" href="#dfn-expanded_term_definition">
expanded
term
definition
</a>
contains
the
<code>
@container
</code>
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
keyword
</a>,
<del class="diff-old">the
</del>
<ins class="diff-chg">its
</ins>
value
<em class="rfc2119" title="must">
must
</em>
be
either
<code>
@list
</code>,
<code>
@set
</code>,
<code>
@language
</code>,
<code>
<ins class="diff-new">@annotation
</ins></code>,
or
be
<a class="tref internalDFN" title="null" href="#dfn-null">
null
</a>.
If
the
value
is
<code>
@language
</code>,
when
the
<a class="tref internalDFN" title="term" href="#dfn-term">
term
</a>
is
used
outside
of
the
<code>
@context
</code>,
the
associated
value
<em class="rfc2119" title="must">
must
</em>
be
a
<del class="diff-old">JSON
object
whose
keys
are
string
s
that
are
[
BCP47
]
</del>
<a class="tref internalDFN" title="language_map" href="#dfn-language_map">
language
<del class="diff-old">identifiers.
The
values
associated
with
each
[
BCP47
</del>
<ins class="diff-chg">map
</ins></a>.<ins class="diff-chg">
If
the
value
is
</ins><code><ins class="diff-chg">
@annotation
</ins></code>,<ins class="diff-chg">
when
the
</ins><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
term
</ins>
</a>
<del class="diff-old">]
language
string
</del>
<ins class="diff-chg">is
used
outside
of
the
</ins><code><ins class="diff-chg">
@context
</ins></code>,<ins class="diff-chg">
the
associated
value
</ins>
<em class="rfc2119" title="must">
must
</em>
be
<del class="diff-old">a
string
or
</del>
an
<del class="diff-old">array
</del>
<a class="tref internalDFN" title="annotation_map" href="#dfn-annotation_map">
<ins class="diff-chg">annotation
map
</ins></a>.</p><p><a class="tref internalDFN" title="term" href="#dfn-term"><ins class="diff-chg">
Terms
</ins>
</a>
<em class="rfc2119" title="must not">
<ins class="diff-new">must
not
</ins></em><ins class="diff-new">
be
used
in
a
circular
manner.
That
is,
the
definition
</ins>
of
<del class="diff-old">string
s.
</del>
<ins class="diff-chg">a
term
cannot
depend
on
the
definition
of
another
term
if
that
other
term
also
depends
on
the
first
term.
</ins>
</p>
<p>
See
<a href="#the-context" class="sec-ref">
<span class="secno">
<del class="diff-old">3.5
</del>
<ins class="diff-chg">5.1
</ins>
</span>
<span class="sec-title">
The
Context
</span>
</a>
and
<a href="#expanded-term-definition" class="sec-ref">
<span class="secno">
<del class="diff-old">4.5
</del>
<ins class="diff-chg">6.5
</ins>
</span>
<span class="sec-title">
Expanded
Term
Definition
</span>
</a>
for
<del class="diff-old">a
</del>
further
discussion
<del class="diff-old">of
</del>
<ins class="diff-chg">on
</ins>
contexts.
</p>
</section>
<del class="diff-old">{
  &quot;@language&quot;: &quot;en&quot;,
  &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
  &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
  &quot;name&quot;: &quot;foaf:name&quot;,
  &quot;depiction&quot;: {&quot;@id&quot;: &quot;foaf:depiction&quot;, &quot;@type&quot;: &quot;@id&quot;},
  &quot;modified&quot;: {&quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;, &quot;@type&quot;: &quot;xsd:dateTime&quot;},
  &quot;homepage&quot;: {&quot;@id&quot;: &quot;foaf:homepage&quot;, &quot;@type&quot;: &quot;@id&quot;, &quot;@container&quot;: &quot;@list&quot;}
}
</del>
</section>
<section class="appendix normative" id="relationship-to-rdf">
<h2>
<span class="secno">
<del class="diff-old">B.
</del>
<ins class="diff-chg">C.
</ins>
</span>
Relationship
to
<del class="diff-old">Other
Linked
Data
Formats
and
Data
Models
</del>
<ins class="diff-chg">RDF
</ins>
</h2>
<p>
<del class="diff-old">This
section
is
non-normative.
Issue
157
</del>
The
<del class="diff-old">intent
of
the
Working
Group
and
the
Editors
of
this
specification
is
to
eventually
align
terminology
used
in
this
document
with
the
terminology
used
in
the
</del>
RDF
<del class="diff-old">Concepts
document
</del>
<ins class="diff-chg">data
model,
as
outlined
in
</ins>
[
<cite>
<a class="bibref" href="#bib-RDF-CONCEPTS">
RDF-CONCEPTS
</a>
</cite>
<del class="diff-old">]
to
the
extent
to
which
it
makes
sense
to
do
so.
In
general,
if
there
</del>
<ins class="diff-chg">],
</ins>
is
an
<del class="diff-old">analogue
to
terminology
used
in
this
document
in
the
RDF
Concepts
document,
the
preference
is
to
use
the
terminology
in
the
RDF
Concepts
document.
JSON-LD
is
a
specification
</del>
<ins class="diff-chg">abstract
syntax
</ins>
for
representing
<del class="diff-old">Linked
Data
in
JSON.
A
common
way
</del>
<ins class="diff-chg">a
directed
graph
</ins>
of
<del class="diff-old">working
with
Linked
Data
</del>
<ins class="diff-chg">information.
It
</ins>
is
<del class="diff-old">through
RDF
,
</del>
<ins class="diff-chg">a
subset
of
</ins><a class="tref internalDFN" title="json-ld_data_model" href="#dfn-json-ld_data_model"><ins class="diff-chg">
JSON-LD's
data
model
</ins></a><ins class="diff-chg">
with
a
few
additional
constraints.
The
differences
between
</ins>
the
<del class="diff-old">Resource
Description
Framework.
RDF
</del>
<ins class="diff-chg">two
data
models
are:
</ins></p><ul><li><ins class="diff-chg">
In
JSON-LD
</ins><a class="tref internalDFN" title="graph_name" href="#dfn-graph_name"><ins class="diff-chg">
graph
names
</ins></a>
can
be
<del class="diff-old">expressed
using
JSON-LD
by
associating
JSON-LD
concepts
such
as
@id
and
@type
with
the
equivalent
</del>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<del class="diff-old">IRI
</del>
<ins class="diff-chg">IRIs
</ins>
</a>
<del class="diff-old">s
</del>
<ins class="diff-chg">or
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
nodes
</ins></a><ins class="diff-chg">
whereas
</ins>
in
<del class="diff-old">RDF.
Further
information
about
</del>
RDF
<del class="diff-old">may
</del>
<ins class="diff-chg">graph
names
have
to
</ins>
be
<del class="diff-old">found
in
the
[
RDF-PRIMER
].
The
JSON-LD
markup
examples
below
demonstrate
how
</del>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<ins class="diff-chg">IRIs
</ins></a>.</li><li><ins class="diff-chg">
In
</ins>
JSON-LD
<a class="tref internalDFN" title="property" href="#dfn-property">
<ins class="diff-new">properties
</ins></a>
can
be
<del class="diff-old">used
to
express
semantic
data
marked
up
</del>
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<ins class="diff-chg">IRIs
</ins></a><ins class="diff-chg">
or
</ins><a class="tref internalDFN" title="blank_node" href="#dfn-blank_node"><ins class="diff-chg">
blank
nodes
</ins></a><ins class="diff-chg">
whereas
</ins>
in
<del class="diff-old">other
languages
and
data
models
such
as
RDF,
Turtle,
RDFa,
Microformats,
and
Microdata.
These
sections
are
merely
provided
as
evidence
that
</del>
<ins class="diff-chg">RDF
properties
(predicates)
have
to
be
</ins><a class="tref internalDFN" title="iri" href="#dfn-iri"><ins class="diff-chg">
IRIs
</ins></a>.</li><li><ins class="diff-chg">
In
contrast
to
RDF
graphs
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph">
JSON-LD
<del class="diff-old">is
very
flexible
in
what
it
can
express
across
different
Linked
Data
</del>
<ins class="diff-chg">graphs
</ins>
</a>
<del class="diff-old">approaches.
Further
information
on
transforming
</del>
<ins class="diff-chg">support
unconnected
</ins><a class="tref internalDFN" title="node" href="#dfn-node"><ins class="diff-chg">
nodes
</ins></a>,<ins class="diff-chg">
i.e.,
nodes
which
are
not
connected
to
any
other
node.
</ins></li><li><ins class="diff-chg">
In
</ins>
JSON-LD
<del class="diff-old">into
RDF
</del>
<ins class="diff-chg">lists
</ins>
are
<del class="diff-old">detailed
in
</del>
<ins class="diff-chg">part
of
</ins>
the
<ins class="diff-new">data
model
whereas
in
RDF
they
are
part
of
a
vocabulary,
namely
</ins>
[
<cite>
<del class="diff-old">JSON-LD-API
</del>
<a class="bibref" href="#bib-RDF-SCHEMA">
<ins class="diff-chg">RDF-SCHEMA
</ins>
</a>
</cite>
].
<del class="diff-old">B.1
</del>
</li>
<li>
RDF
<ins class="diff-chg">values
are
either
typed
</ins>
<em>
<del class="diff-old">This
section
is
non-normative.
</del>
<ins class="diff-chg">literals
</ins>
</em>
<del class="diff-old">The
RDF
</del>
<ins class="diff-chg">(
</ins><a class="tref internalDFN" title="typed_value" href="#dfn-typed_value"><ins class="diff-chg">
typed
values
</ins></a><ins class="diff-chg">
)
or
</ins><em><ins class="diff-chg">
language-tagged
strings
</ins></em><ins class="diff-chg">
(
</ins><a class="tref internalDFN" title="language-tagged_string" href="#dfn-language-tagged_string"><ins class="diff-chg">
language-tagged
strings
</ins></a><ins class="diff-chg">
)
whereas
JSON-LD
also
supports
JSON's
native
</ins>
data
<del class="diff-old">model,
as
outlined
in
</del>
<ins class="diff-chg">types,
i.e.,
</ins><a class="tref internalDFN" title="number" href="#dfn-number"><ins class="diff-chg">
number
</ins></a>,<a class="tref internalDFN" title="string" href="#dfn-string"><ins class="diff-chg">
strings
</ins></a>,<ins class="diff-chg">
and
the
boolean
values
</ins><a class="tref internalDFN" title="true" href="#dfn-true"><ins class="diff-chg">
true
</ins></a><ins class="diff-chg">
and
</ins><a class="tref internalDFN" title="false" href="#dfn-false"><ins class="diff-chg">
false
</ins></a>.<ins class="diff-chg">
The
JSON-LD
API
</ins>
[
<cite>
<del class="diff-old">RDF-CONCEPTS
</del>
<a class="bibref" href="#bib-JSON-LD-API">
<ins class="diff-chg">JSON-LD-API
</ins>
</a>
</cite>
<del class="diff-old">],
is
an
abstract
syntax
for
representing
a
directed
graph
of
information.
</del>
<ins class="diff-chg">]
specification
defines
the
conversion
rules
between
JSON's
native
data
types
and
RDF's
counterparts
to
allow
full
round-tripping.
</ins></li></ul><p><ins class="diff-chg">
Summarized
these
differences
mean
that
</ins>
JSON-LD
is
capable
of
serializing
any
RDF
<del class="diff-old">graph,
</del>
<ins class="diff-chg">graph
or
dataset
</ins>
and
<del class="diff-old">performing
full
RDF
to
</del>
<ins class="diff-chg">most,
but
not
all,
</ins>
JSON-LD
<ins class="diff-new">documents
can
be
transformed
</ins>
to
<del class="diff-old">RDF
round-tripping.
</del>
<ins class="diff-chg">RDF.
</ins>
A
complete
description
of
<del class="diff-old">how
JSON-LD
maps
to
RDF
and
</del>
<ins class="diff-chg">the
</ins>
algorithms
<del class="diff-old">detailing
how
one
can
</del>
<ins class="diff-chg">to
</ins>
convert
from
RDF
to
JSON-LD
and
from
JSON-LD
to
RDF
<del class="diff-old">are
</del>
<ins class="diff-chg">is
</ins>
included
in
the
JSON-LD
API
[
<cite>
<a class="bibref" href="#bib-JSON-LD-API">
JSON-LD-API
</a>
</cite>
]
specification.
</p>
<p>
<ins class="diff-new">Even
though
</ins>
JSON-LD
<del class="diff-old">allows
properties
to
be
BNodes,
while
</del>
<ins class="diff-chg">serializes
</ins>
RDF
<del class="diff-old">does
not.
Expressing
properties
</del>
<ins class="diff-chg">datasets,
it
can
also
be
used
</ins>
as
<del class="diff-old">BNodes
in
JSON-LD
</del>
<ins class="diff-chg">a
RDF
graph
source.
In
that
case,
a
consumer
</ins><em class="rfc2119" title="must"><ins class="diff-chg">
must
</ins></em>
only
<del class="diff-old">becomes
an
issue
(and
could
raise
an
exception)
when
it
is
transformed
</del>
<ins class="diff-chg">use
the
default
graph
and
ignore
all
named
graphs.
This
allows
servers
</ins>
to
<del class="diff-old">RDF.
</del>
<ins class="diff-chg">expose
data
in,
e.g.,
both
Turtle
and
JSON-LD
using
content
negotiation.
</ins>
</p>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
<ins class="diff-new">Publishers
supporting
both
dataset
and
graph
syntaxes
have
to
ensure
</ins>
that
the
<del class="diff-old">JSON-LD
</del>
<ins class="diff-chg">primary
</ins>
data
<del class="diff-old">model
</del>
is
<del class="diff-old">silent
on
the
topic
of
unlabeled
nodes
.
Nevertheless,
this
specification
allows
for
the
expression
of
unlabeled
nodes
,
as
most
graph-based
data
sets
on
</del>
<ins class="diff-chg">stored
in
</ins>
the
<del class="diff-old">Web
contain
a
number
of
associated
nodes
</del>
<ins class="diff-chg">default
graph
to
enable
consumers
</ins>
that
<del class="diff-old">are
</del>
<ins class="diff-chg">do
</ins>
not
<del class="diff-old">named
</del>
<ins class="diff-chg">support
datasets
to
process
the
information.
</ins></p></div></section><section class="appendix informative" id="relationship-to-other-linked-data-formats"><h2><span class="secno"><ins class="diff-chg">
D.
</ins></span><ins class="diff-chg">
Relationship
to
Other
Linked
Data
Formats
</ins></h2><p><em><ins class="diff-chg">
This
section
is
non-normative.
</ins></em></p><p><ins class="diff-chg">
The
JSON-LD
markup
examples
below
demonstrate
how
JSON-LD
can
be
used
to
express
semantic
data
marked
up
in
other
linked
data
formats
such
as
Turtle,
RDFa,
Microformats,
</ins>
and
<del class="diff-old">thus
</del>
<ins class="diff-chg">Microdata.
These
sections
</ins>
are
<del class="diff-old">not
directly
de-referenceable.
</del>
<ins class="diff-chg">merely
provided
as
evidence
that
JSON-LD
is
very
flexible
in
what
it
can
express
across
different
</ins><a class="tref internalDFN" title="linked_data" href="#dfn-linked_data"><ins class="diff-chg">
Linked
Data
</ins></a><ins class="diff-chg">
approaches.
</ins>
</p>
<section id="turtle">
<h3>
<span class="secno">
<del class="diff-old">B.1.1
</del>
<ins class="diff-chg">D.1
</ins>
</span>
Turtle
</h3>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
The
following
are
examples
of
converting
RDF
expressed
in
[
<cite>
<a class="bibref" href="#bib-TURTLE-TR">
TURTLE-TR
</a>
</cite>
]
into
JSON-LD.
</p>
<section id="prefix-definitions">
<h4>
<span class="secno">
<del class="diff-old">B.1.1.1
</del>
<ins class="diff-chg">D.1.1
</ins>
</span>
Prefix
definitions
</h4>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
The
JSON-LD
context
has
direct
equivalents
for
the
Turtle
<code>
@prefix
</code>
declaration:
</p>
<del class="diff-old">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
</del>
<div class="example"><div class="example-title"><span>Example 61</span>: A set of statements serialized in Turtle</div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
&lt;http://manu.sporny.org/i/public&gt; a foaf:Person;
  foaf:name &quot;Manu Sporny&quot;;
foaf:homepage
&lt;http://manu.sporny.org/&gt;
.
</pre>
</div>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 62</span>: The same set of statements serialized in JSON-LD</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
  },
  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
  &quot;@type&quot;: &quot;foaf:Person&quot;,
  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
  &quot;foaf:homepage&quot;: { &quot;@id&quot;: &quot;http://manu.sporny.org/&quot; }
}
</pre>
</div>
<div class="note">
<div class="note-title">
<span>
Note
</span>
</div>
<p class="">
JSON-LD
has
no
equivalent
for
the
Turtle
<code>
@base
</code>
declaration.
</p>
</div>
</section>
<section id="embedding-1">
<h4>
<span class="secno">
<del class="diff-old">B.1.1.2
</del>
<ins class="diff-chg">D.1.2
</ins>
</span>
Embedding
</h4>
<p>
Both
Turtle
and
JSON-LD
allow
embedding,
although
Turtle
only
allows
embedding
of
<del class="diff-old">unlabeled
</del>
<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
<ins class="diff-chg">blank
</ins>
nodes
</a>.
</p>
</section>
<del class="diff-old">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
</del>
<div class="example"><div class="example-title"><span>Example 63</span>: Embedding in Turtle</div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
&lt;http://manu.sporny.org/i/public&gt;
  a foaf:Person;
  foaf:name &quot;Manu Sporny&quot;;
foaf:knows
[
a
foaf:Person;
foaf:name
&quot;Gregg
Kellogg&quot;
]
.
</pre>
</div>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 64</span>: Same embedding example in JSON-LD</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
  },
  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
  &quot;@type&quot;: &quot;foaf:Person&quot;,
  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
  &quot;foaf:knows&quot;:
  {
    &quot;@type&quot;: &quot;foaf:Person&quot;,
    &quot;foaf:name&quot;: &quot;Gregg Kellogg&quot;
  }
}
</pre>
</div>
<section id="lists">
<h4>
<span class="secno">
<del class="diff-old">B.1.1.3
</del>
<ins class="diff-chg">D.1.3
</ins>
</span>
Lists
</h4>
<p>
Both
JSON-LD
and
Turtle
can
represent
sequential
lists
of
values.
</p>
<del class="diff-old">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
</del>
<div class="example"><div class="example-title"><span>Example 65</span>: A list of values in Turtle</div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
&lt;http://example.org/people#joebob&gt; a foaf:Person;
  foaf:name &quot;Joe Bob&quot;;
foaf:nick
(
&quot;joe&quot;
&quot;bob&quot;
&quot;jaybee&quot;
)
.
</pre>
</div>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 66</span>: Same example with a list of values in JSON-LD</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
  },
  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
  &quot;@type&quot;: &quot;foaf:Person&quot;,
  &quot;foaf:name&quot;: &quot;Joe Bob&quot;,
  &quot;foaf:nick&quot;:
  {
    &quot;@list&quot;: [ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]
  }
}
</pre>
</div>
</section>
</section>
<section id="rdfa">
<h3>
<span class="secno">
<del class="diff-old">B.1.2
</del>
<ins class="diff-chg">D.2
</ins>
</span>
RDFa
</h3>
<p>
The
following
example
describes
three
people
with
their
respective
names
and
homepages.
</p>
<del class="diff-old">&gt;
</del>
<div class="example"><div class="example-title"><span>Example 67</span>: RDFa fragment that describes three people</div><pre class="example">&lt;div <span class="diff">prefix=&quot;foaf: http://xmlns.com/foaf/0.1/&quot;</span>&gt;
   &lt;ul&gt;
      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/bob/&quot; property=&quot;foaf:name&quot; </span>&gt;Bob&lt;/a&gt;
      &lt;/li&gt;
      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/eve/&quot; property=&quot;foaf:name&quot; </span>&gt;Eve&lt;/a&gt;
      &lt;/li&gt;
      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/manu/&quot; property=&quot;foaf:name&quot; </span>&gt;Manu&lt;/a&gt;
      &lt;/li&gt;
   &lt;/ul&gt;
&lt;/div&gt;
</pre>
</div>
<p>
An
example
JSON-LD
implementation
using
a
single
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
is
described
below.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 68</span>: Same description in JSON-LD (context shared among node objects)</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
  },
  &quot;@graph&quot;:
  [
    {
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;foaf:homepage&quot;: &quot;http://example.com/bob/&quot;,
      &quot;foaf:name&quot;: &quot;Bob&quot;
    },
    {
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;foaf:homepage&quot;: &quot;http://example.com/eve/&quot;,
      &quot;foaf:name&quot;: &quot;Eve&quot;
    },
    {
      &quot;@type&quot;: &quot;foaf:Person&quot;,
      &quot;foaf:homepage&quot;: &quot;http://example.com/manu/&quot;,
      &quot;foaf:name&quot;: &quot;Manu&quot;
    }
  ]
}
</pre>
</div>
</section>
<section id="microformats">
<h3>
<span class="secno">
<del class="diff-old">B.1.3
</del>
<ins class="diff-chg">D.3
</ins>
</span>
Microformats
</h3>
<p>
The
following
example
uses
a
simple
Microformats
hCard
example
to
express
how
the
Microformat
is
represented
in
JSON-LD.
</p>
<del class="diff-old">&lt;div class=&quot;vcard&quot;&gt;
</del>
<div class="example"><div class="example-title"><span>Example 69</span>: HTML fragment with a simple Microformats hCard</div><pre class="example">&lt;div class=&quot;vcard&quot;&gt;
 &lt;a class=&quot;url fn&quot; href=&quot;http://tantek.com/&quot;&gt;Tantek Çelik&lt;/a&gt;
&lt;/div&gt;
</pre>
</div>
<p>
The
representation
of
the
hCard
expresses
the
Microformat
terms
in
the
<a class="tref internalDFN" title="context" href="#dfn-context">
context
</a>
and
uses
them
directly
for
the
<code>
url
</code>
and
<code>
fn
</code>
properties.
Also
note
that
the
Microformat
to
JSON-LD
processor
has
generated
the
proper
URL
type
for
<code>
http://tantek.com/
</code>.
</p>
<del class="diff-old">{
</del>
<div class="example"><div class="example-title"><span>Example 70</span>: Same hCard representation in JSON-LD</div><pre class="example">{
  &quot;@context&quot;:
  {
    &quot;vcard&quot;: &quot;http://microformats.org/profile/hcard#vcard&quot;,
    &quot;url&quot;:
    {
      &quot;@id&quot;: &quot;http://microformats.org/profile/hcard#url&quot;,
      &quot;@type&quot;: &quot;@id&quot;
    },
    &quot;fn&quot;: &quot;http://microformats.org/profile/hcard#fn&quot;
  },
  &quot;@type&quot;: &quot;vcard&quot;,
  &quot;url&quot;: &quot;http://tantek.com/&quot;,
  &quot;fn&quot;: &quot;Tantek Çelik&quot;
}
</pre>
</div>
</section>
<section id="microdata">
<h3>
<span class="secno">
<del class="diff-old">B.1.4
</del>
<ins class="diff-chg">D.4
</ins>
</span>
Microdata
</h3>
<p>
The
microdata
example
below
expresses
book
information
as
a
microdata
Work
item.
</p>
<del class="diff-old">&lt;dl itemscope
</del>
<div class="example"><div class="example-title"><span>Example 71</span>: HTML fragments that describes a book using microdata</div><pre class="example">&lt;dl itemscope
    itemtype=&quot;http://purl.org/vocab/frbr/core#Work&quot;
    itemid=&quot;http://purl.oreilly.com/works/45U8QJGZSQKDH8N&quot;&gt;
 &lt;dt&gt;Title&lt;/dt&gt;
 &lt;dd&gt;&lt;cite itemprop=&quot;http://purl.org/dc/terms/title&quot;&gt;Just a Geek&lt;/cite&gt;&lt;/dd&gt;
 &lt;dt&gt;By&lt;/dt&gt;
 &lt;dd&gt;&lt;span itemprop=&quot;http://purl.org/dc/terms/creator&quot;&gt;Wil Wheaton&lt;/span&gt;&lt;/dd&gt;
 &lt;dt&gt;Format&lt;/dt&gt;
 &lt;dd itemprop=&quot;http://purl.org/vocab/frbr/core#realization&quot;
     itemscope
     itemtype=&quot;http://purl.org/vocab/frbr/core#Expression&quot;
     itemid=&quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;&gt;
  &lt;link itemprop=&quot;http://purl.org/dc/terms/type&quot; href=&quot;http://purl.oreilly.com/product-types/BOOK&quot;&gt;
  Print
 &lt;/dd&gt;
 &lt;dd itemprop=&quot;http://purl.org/vocab/frbr/core#realization&quot;
     itemscope
     itemtype=&quot;http://purl.org/vocab/frbr/core#Expression&quot;
     itemid=&quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;&gt;
  &lt;link itemprop=&quot;http://purl.org/dc/terms/type&quot; href=&quot;http://purl.oreilly.com/product-types/EBOOK&quot;&gt;
  Ebook
 &lt;/dd&gt;
&lt;/dl&gt;
</pre>
</div>
<p>
Note
that
the
JSON-LD
representation
of
the
Microdata
information
stays
true
to
the
desires
of
the
Microdata
community
to
avoid
contexts
and
instead
refer
to
items
by
their
full
<a class="tref internalDFN" title="iri" href="#dfn-iri">
<abbr title="Internationalized Resource Identifier">
IRI
</abbr>
</a>.
</p>
<del class="diff-old">[
</del>
<div class="example"><div class="example-title"><span>Example 72</span>: Same book description in JSON-LD (avoiding contexts)</div><pre class="example">[
  {
    &quot;@id&quot;: &quot;http://purl.oreilly.com/works/45U8QJGZSQKDH8N&quot;,
    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Work&quot;,
    &quot;http://purl.org/dc/terms/title&quot;: &quot;Just a Geek&quot;,
    &quot;http://purl.org/dc/terms/creator&quot;: &quot;Whil Wheaton&quot;,
    &quot;http://purl.org/vocab/frbr/core#realization&quot;:
    [
      &quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;,
      &quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;
    ]
  },
  {
    &quot;@id&quot;: &quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;,
    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Expression&quot;,
    &quot;http://purl.org/dc/terms/type&quot;: &quot;http://purl.oreilly.com/product-types/BOOK&quot;
  },
  {
    &quot;@id&quot;: &quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;,
    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Expression&quot;,
    &quot;http://purl.org/dc/terms/type&quot;: &quot;http://purl.oreilly.com/product-types/EBOOK&quot;
  }
]
</pre>
</div>
</section>
</section>
<section class="appendix informative" id="iana-considerations">
<h2>
<span class="secno">
<del class="diff-old">B.2
</del>
<ins class="diff-chg">E.
</ins>
</span>
IANA
Considerations
</h2>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
This
section
is
included
merely
for
standards
community
review
and
will
be
submitted
to
the
Internet
Engineering
Steering
Group
if
this
specification
becomes
a
<abbr title="World Wide Web Consortium">
W3C
</abbr>
Recommendation.
</p>
<h2 id="application-ld-json">
application/ld+json
</h2>
<dl>
<dt>
Type
name:
</dt>
<dd>
application
</dd>
<dt>
Subtype
name:
</dt>
<dd>
ld+json
</dd>
<dt>
Required
parameters:
</dt>
<dd>
None
</dd>
<dt>
Optional
parameters:
</dt>
<dd>
<dl>
<dt>
<code>
form
</code>
</dt>
<dd>
Determines
the
serialization
form
for
the
JSON-LD
document.
The
only
valid
value
at
the
moment
is
<code>
expanded
</code>.
If
no
form
is
specified
in
an
HTTP
request
header
to
an
HTTP
server,
the
server
<em class="rfc2119" title="may">
may
</em>
choose
any
form.
If
no
form
is
specified
in
an
HTTP
response,
the
form
<em class="rfc2119" title="must not">
must
not
</em>
be
assumed
to
take
any
particular
form.
</dd>
</dl>
<dl>
<dt>
<code>
<ins class="diff-new">profile
</ins></code></dt><dd><ins class="diff-new">
A
whitespace-separated
list
of
IRIs
identifying
specific
constraints
or
conventions
that
apply
to
a
JSON-LD
document.
A
profile
</ins><em class="rfc2119" title="must not"><ins class="diff-new">
must
not
</ins></em><ins class="diff-new">
change
the
semantics
of
the
resource
representation
when
processed
without
profile
knowledge,
so
that
clients
both
with
and
without
knowledge
of
a
profiled
resource
can
safely
use
the
same
representation.
The
</ins><code><ins class="diff-new">
profile
</ins></code><ins class="diff-new">
parameter
</ins><em class="rfc2119" title="may"><ins class="diff-new">
may
</ins></em><ins class="diff-new">
also
be
used
by
clients
to
express
their
preferences
in
the
content
negotiation
process.
It
is
</ins><em class="rfc2119" title="recommended"><ins class="diff-new">
recommended
</ins></em><ins class="diff-new">
that
profile
IRIs
are
dereferenceable
and
provide
useful
documentation
at
that
</ins><abbr title="Internationalized Resource Identifier"><ins class="diff-new">
IRI
</ins></abbr>.<ins class="diff-new">
This
specification,
however,
does
not
define
any
formats
for
such
profile
descriptions.
</ins></dd></dl>
</dd>
<dt>
Encoding
considerations:
</dt>
<dd>
The
same
as
the
<code>
application/json
</code>
MIME
media
type.
</dd>
<dt>
Security
considerations:
</dt>
<dd>
Since
JSON-LD
is
intended
to
be
a
pure
data
exchange
format
for
directed
graphs,
the
serialization
<em class="rfc2119" title="should not">
should
not
</em>
be
passed
through
a
code
execution
mechanism
such
as
JavaScript's
<code>
eval()
</code>
function.
It
is
<em class="rfc2119" title="recommended">
recommended
</em>
that
a
conforming
parser
does
not
attempt
to
directly
evaluate
the
JSON-LD
serialization
and
instead
purely
parse
the
input
into
a
language-native
data
structure.
</dd>
<dt>
Interoperability
considerations:
</dt>
<dd>
Not
Applicable
</dd>
<dt>
Published
specification:
</dt>
<dd>
The
<a href="http://json-ld.org/spec/latest/">
JSON-LD
</a>
specification.
</dd>
<dt>
Applications
that
use
this
media
type:
</dt>
<dd>
Any
programming
environment
that
requires
the
exchange
of
directed
graphs.
Implementations
of
JSON-LD
have
been
created
for
JavaScript,
Python,
Ruby,
PHP
and
C++.
</dd>
<dt>
Additional
information:
</dt>
<dd>
<dl>
<dt>
Magic
number(s):
</dt>
<dd>
Not
Applicable
</dd>
<dt>
File
extension(s):
</dt>
<dd>.jsonld
</dd>
<dt>
Macintosh
file
type
code(s):
</dt>
<dd>
TEXT
</dd>
</dl>
</dd>
<dt>
Person
&amp;
email
address
to
contact
for
further
information:
</dt>
<dd>
Manu
Sporny
&lt;msporny@digitalbazaar.com&gt;
</dd>
<dt>
Intended
usage:
</dt>
<dd>
Common
</dd>
<dt>
Restrictions
on
usage:
</dt>
<dd>
None
</dd>
<dt>
Author(s):
</dt>
<dd>
Manu
Sporny,
Gregg
Kellogg,
Markus
Lanthaler,
Dave
Longley
</dd>
<dt>
Change
controller:
</dt>
<dd>
<abbr title="World Wide Web Consortium">
W3C
</abbr>
</dd>
</dl>
<p>
Fragment
identifiers
used
with
<a href="#application-ld-json">
application/ld+json
</a>
resources
<em class="rfc2119" title="may">
may
</em>
identify
a
node
in
<del class="diff-old">the
linked
data
</del>
<ins class="diff-chg">a
</ins><a class="tref internalDFN" title="json-ld_graph" href="#dfn-json-ld_graph"><ins class="diff-chg">
JSON-LD
</ins>
graph
</a>
expressed
in
the
resource.
This
idiom,
which
is
also
used
in
RDF
[
<cite>
<a class="bibref" href="#bib-RDF-CONCEPTS">
RDF-CONCEPTS
</a>
</cite>
],
gives
a
simple
way
to
&quot;mint&quot;
new,
document-local
IRIs
to
label
nodes
and
therefore
contributes
considerably
to
the
expressive
power
of
JSON-LD.
</p>
</section>
<section class="appendix informative" id="acknowledgements">
<h2>
<span class="secno">
<del class="diff-old">B.3
</del>
<ins class="diff-chg">F.
</ins>
</span>
Acknowledgements
</h2>
<p>
<em>
This
section
is
non-normative.
</em>
</p>
<p>
A
large
amount
of
thanks
goes
out
to
the
JSON-LD
Community
Group
participants
who
worked
through
many
of
the
technical
issues
on
the
mailing
list
and
the
weekly
telecons
-
of
special
mention
are
Niklas
Lindström,
François
Daoust,
<ins class="diff-new">Lin
Clark,
</ins>
and
Zdenko
'Denny'
Vrandečić.
The
editors
would
like
to
thank
Mark
Birbeck,
who
provided
a
great
deal
of
the
initial
push
behind
the
JSON-LD
work
via
his
work
on
RDFj.
The
work
of
Dave
Lehn
and
Mike
Johnson
are
appreciated
for
reviewing,
and
performing
several
implementations
of
the
specification.
Ian
Davis
is
thanked
for
this
work
on
RDF/JSON.
Thanks
also
to
Nathan
Rixham,
Bradley
P.
Allen,
Kingsley
Idehen,
Glenn
McDonald,
Alexandre
Passant,
Danny
Ayers,
Ted
Thibodeau
Jr.,
Olivier
Grisel,
Josh
Mandel,
Eric
Prud'hommeaux,
David
Wood,
Guus
Schreiber,
Pat
Hayes,
Sandro
Hawke,
and
Richard
Cyganiak
for
their
input
on
the
specification.
</p>
</section>
<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
<h2>
<span class="secno">
<del class="diff-old">C.
</del>
<ins class="diff-chg">G.
</ins>
</span>
References
</h2>
<section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">C.1
</del>
<ins class="diff-chg">G.1
</ins>
</span>
Normative
references
</h3>
<dl class="bibliography" about="">
<dt id="bib-BCP47">
[BCP47]
</dt>
<dd rel="dcterms:requires">
A.
Phillips;
M.
Davis.
<a href="http://tools.ietf.org/html/bcp47">
<cite>
Tags
for
Identifying
Languages
</cite>
</a>
September
2009.
IETF
Best
Current
Practice.
URL:
<a href="http://tools.ietf.org/html/bcp47">
http://tools.ietf.org/html/bcp47
</a>
</dd>
<dt id="bib-RDF-CONCEPTS">
[RDF-CONCEPTS]
</dt>
<dd rel="dcterms:requires">
<cite>
<a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">
RDF
1.1
Concepts
and
Abstract
Syntax
</a>
</cite>
Richard
Cyganiak,
David
Wood,
Editors.
World
Wide
Web
Consortium
(work
in
progress).
30
May
2012.
Editor's
Draft.
This
edition
of
the
JSON-LD
Syntax
specification
is
http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/.
The
<a href="http://www.w3.org/TR/rdf11-concepts/">
latest
edition
of
the
JSON-LD
Syntax
</a>
is
available
at
http://www.w3.org/TR/rdf11-concepts/
</dd>
<dt id="bib-RFC2119">
<ins class="diff-new">[RFC2119]
</ins></dt><dd rel="dcterms:requires"><ins class="diff-new">
S.
Bradner.
</ins><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite><ins class="diff-new">
Key
words
for
use
in
RFCs
to
Indicate
Requirement
Levels.
</ins></cite></a><ins class="diff-new">
March
1997.
Internet
RFC
2119.
URL:
</ins><a href="http://www.ietf.org/rfc/rfc2119.txt"><ins class="diff-new">
http://www.ietf.org/rfc/rfc2119.txt
</ins></a></dd>
<dt id="bib-RFC3987">
[RFC3987]
</dt>
<dd rel="dcterms:requires">
M.
Dürst;
M.
Suignard.
<a href="http://www.ietf.org/rfc/rfc3987.txt">
<cite>
Internationalized
Resource
Identifiers
(IRIs).
</cite>
</a>
January
2005.
Internet
RFC
3987.
URL:
<a href="http://www.ietf.org/rfc/rfc3987.txt">
http://www.ietf.org/rfc/rfc3987.txt
</a>
</dd>
<dt id="bib-RFC4627">
[RFC4627]
</dt>
<dd rel="dcterms:requires">
D.
Crockford.
<a href="http://www.ietf.org/rfc/rfc4627.txt">
<cite>
The
application/json
Media
Type
for
JavaScript
Object
Notation
(JSON)
</cite>
</a>
July
2006.
Internet
RFC
4627.
URL:
<a href="http://www.ietf.org/rfc/rfc4627.txt">
http://www.ietf.org/rfc/rfc4627.txt
</a>
</dd>
<dt id="bib-RFC5988">
[RFC5988]
</dt>
<dd rel="dcterms:requires">
<cite>
<a href="http://tools.ietf.org/rfc/rfc5988">
Web
Linking
</a>
</cite>
M.
Nottingham.
Editor.
October
2010.
IETF
Standard.
URL:
<a href="http://tools.ietf.org/rfc/rfc5988.txt">
http://tools.ietf.org/rfc/rfc5988.txt
</a>
</dd>
</dl>
</section>
<section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter">
<h3>
<span class="secno">
<del class="diff-old">C.2
</del>
<ins class="diff-chg">G.2
</ins>
</span>
Informative
references
</h3>
<dl class="bibliography" about="">
<dt id="bib-JSON-LD-API">
[JSON-LD-API]
</dt>
<dd rel="dcterms:references">
<cite>
<a href="http://json-ld.org/spec/ED/json-ld-api/20120524/">
The
JSON-LD
API
1.0
</a>
</cite>
Manu
Sporny,
Gregg
Kellogg,
Dave
Longley,
Markus
Lanthaler,
Editors.
World
Wide
Web
Consortium
(work
in
progress).
24
May
2012.
Editor's
Draft.
This
edition
of
the
JSON-LD
Syntax
specification
is
http://json-ld.org/spec/ED/json-ld-api/20120524/.
The
<a href="http://json-ld.org/spec/latest/json-ld-api/">
latest
edition
of
the
JSON-LD
Syntax
</a>
is
available
at
http://json-ld.org/spec/latest/json-ld-api/
</dd>
<del class="diff-old">[RDF-PRIMER]
</del>
<dt id="bib-RDF-SCHEMA">
<ins class="diff-chg">[RDF-SCHEMA]
</ins>
</dt>
<del class="diff-old">Frank
Manola;
Eric
Miller.
</del>
<dd rel="dcterms:references">
<ins class="diff-chg">Dan
Brickley;
Ramanathan
V.
Guha.
</ins><a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">
<cite>
RDF
<del class="diff-old">Primer.
</del>
<ins class="diff-chg">Vocabulary
Description
Language
1.0:
RDF
Schema.
</ins>
</cite>
</a>
10
February
2004.
W3C
Recommendation.
URL:
<del class="diff-old">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/
[RDF-SPARQL-QUERY]
Andy
Seaborne;
Eric
Prud'hommeaux.
SPARQL
Query
Language
for
RDF.
15
January
2008.
W3C
Recommendation.
URL:
http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115
</del>
<a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">
<ins class="diff-chg">http://www.w3.org/TR/2004/REC-rdf-schema-20040210
</ins>
</a>
</dd>
<dt id="bib-RDFA-CORE">
[RDFA-CORE]
</dt>
<dd rel="dcterms:references">
Shane
McCarron;
et
al.
<a href="http://www.w3.org/TR/2012/REC-rdfa-core-20120607/">
<cite>
RDFa
Core
1.1:
Syntax
and
processing
rules
for
embedding
RDF
through
attributes.
</cite>
</a>
7
June
2012.
W3C
Recommendation.
URL:
<a href="http://www.w3.org/TR/2012/REC-rdfa-core-20120607/">
http://www.w3.org/TR/2012/REC-rdfa-core-20120607/
</a>
</dd>
<dt id="bib-TURTLE-TR">
[TURTLE-TR]
</dt>
<dd rel="dcterms:references">
Eric
Prud'hommeaux,
Gavin
Carothers.
<cite>
<a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">
Turtle:
Terse
RDF
Triple
Language.
</a>
</cite>
09
August
2011.
W3C
Working
Draft.
URL:
<a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">
http://www.w3.org/TR/2011/WD-turtle-20110809/
</a>
</dd>
</dl>
</section>
</section>
</body>
</html>
